Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a repackaging configuration option that keeps certain resources in the root of the jar #7035

Closed
wilkinsona opened this issue Sep 27, 2016 · 3 comments
Labels
status: duplicate A duplicate of another issue

Comments

@wilkinsona
Copy link
Member

wilkinsona commented Sep 27, 2016

Cloud Foundry supports pre-runtime hooks that need to be placed in the root of an application's directory. When you're deploying a fat jar or war archive, that means they need to go in the root of the archive. This has always been a problem with wars (where resources end up in WEB-INF/classes) and, since the move to BOOT-INF/classes in 1.4, it's now a problem with jars too.

We should provide a repackaging configuration option that allows certain resources to remain in the root of the archive.

@wilkinsona wilkinsona added type: enhancement A general enhancement for: team-attention An issue we'd like other members of the team to review labels Sep 27, 2016
@kelapure
Copy link

For standalone deployable war files you can create the custom top level folder in /src/main/webapp/ like /src/main/webapp/.profile.d

@wilkinsona
Copy link
Member Author

Ah, yes. Of course you can. Thanks, @kelapure.

@wilkinsona
Copy link
Member Author

It's just occurred to me that this is really the same requirements as #6626.

@wilkinsona wilkinsona added status: duplicate A duplicate of another issue and removed type: enhancement A general enhancement for: team-attention An issue we'd like other members of the team to review labels Sep 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

2 participants