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
A fat jar built with Gradle moves META-INF beneath BOOT-INF/classes while Maven leaves it at the jar's root #28562
Comments
I discovered the difference when attempting to build container images for use with Dataflow. The labels it uses to fill in the configuration weren't present when built via gradle but are when built via maven. Some steps to reproduce the issue: The expected behavior when using Maven can be seen via the following steps:
While the following shows the resources in the wrong location, thus not getting recognized for label generation:
|
Thanks, @nrheckman. The problem can also be reproduced using |
The changes for gh-28562 attempted to align the Gradle plugin's handling of META-INF with the Maven plugin's behavior. Unfortunately, they want too far, applying the handling to both jar and war files when the Maven plugin only applies it to jar files. This commit reworks the changes so that they only apply to jar files. Closes gh-30026
With a few exceptions, the Maven repackaging leaves
META-INF
at the root of the jar. With Gradle, everything gets moved beneathBOOT-INF/classes
.The text was updated successfully, but these errors were encountered: