-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Gradle plugin: declare task dependencies for Gradle 7.0 Milestone 1 #25126
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
Comments
It's a little odd that Gradle thinks that various tasks in Gradle's confusion is due to the output location of
#23797 will address this by configuring a classifier by default so I'm going to close this issue as a duplicate. I think it's probably also worth reporting this issue to the Gradle team to explore if it's correct that Gradle is considering disabled tasks during its validation process. If you open an issue, please comment here with a link to it so that we can follow along. With all of that said, if you're using
|
I've opened spring-guides/gs-multi-module#40 so that the guide can be corrected. |
Thank you! Adding the classifier helped. I'm looking into the other recommendation now. |
I'm using Gradle 7.0 Milestone 1, Spring Boot 2.4.2, and 2.4.2 for the spring-boot-gradle-plugin. I have a simple Gradle project with two subprojects (sub1, sub2). While
sub2
is a regular Spring Boot project that depends onsub1
,sub1
is used as a library. As described in https://spring.io/guides/gs/multi-module/ I disabled thebootJar
task in the library subprojectsub1
.During a build with Gradle 7.0 Milestone 1 I experience the errors shown below.
Example project: https://github.com/C-Otto/gradle7springboot
The text was updated successfully, but these errors were encountered: