-
Notifications
You must be signed in to change notification settings - Fork 9
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
Undo api
-> implementation
of Spring Boot and Dependency management plugin
#299
Comments
While I acknowledge what you are saying, I'm not sure that having these dependencies on the compile classpath of all downstream projects is the correct way to solve this. Also, I believe the A better way, would perhaps be if these dependencies were added to Regarding the change in patch release version, these dependencies were (to my understanding) never meant to be exposed, but it could not be prevented with previous versions of Gradles |
I don't understand the reasoning behind 42ba793
(Besides, this was done in a patch version of Grails and broke my build, that shouldn't happen)
My thinking:
buildSrc
.buildSrc
, it is idiomatic to have some references to e.g.org.springframework.boot.gradle.plugin.SpringBootPlugin
, e.g. for dependency managementorg.springframework.boot:spring-boot-gradle-plugin
needs to be on the compile classpath ofbuildSrc
6.1.2
, whereorg.springframework.boot:spring-boot-gradle-plugin
was stillapi
, I could do the following:I didn't have to specify versions for the other two plugins.
The text was updated successfully, but these errors were encountered: