-
Notifications
You must be signed in to change notification settings - Fork 40.6k
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
Gradle POM-only dependencies cause jar application loader to fail #16001
Comments
For the record, the Maven plugin seems to skip |
We just package whatever is on the classpath, with directories going into |
Just as an FYI, from the linked Gradle issue, I did some investigation and found that pom files for dependencies with So Gradle is consistent with Maven there. |
I stand corrected. Thanks, @ljacomet. I'm also surprised that Maven behaves the way that it does, but there are probably good reasons for it of which I am ignorant. Our Maven support for building fat jars is already written in such a way that it'll ignore a pom. Our Gradle support has been updated in 59430a2 to behave the same way. |
Same surprise, assumptions on the reasons and ignorance here 😉 |
Dependencies with pom packaging are included on the classpath and the boot jar process nor the loader considers the type of the file cause application startup to fail.
To reproduce take the following build:
Run
bootJar
and runjava -jar build/libs/spring.jar
and note the failure:POM files can be expected on configurations for either
pom
packaged dependencies like this, or forpom
dependency management files for new native BOM support.Gradle version:
The text was updated successfully, but these errors were encountered: