You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @jjohannes, Thank you for all the effort you have put into this repo and for sharing your knowledge about Gradle through your fantastic compilation of videos on YouTube.
I was reviewing the setup project for Java + Spring Boot that you have shared, and I noticed that the id("io.spring.dependency-management") version "1.1.4" plugin, which provides dependency version resolution for all Spring Boot based projects, was not used.
I am curious to know why you chose not to use this plugin. I would appreciate it if you could share your thoughts on this matter.
The text was updated successfully, but these errors were encountered:
Hi @randyhbh. Thanks for the feedback and the question. 🙏
I think the docs on the id("io.spring.dependency-management") are not very clear on this topic. Since Gradle 6, Gradle fully supports using BOMs directly. Which in most cases makes the plugin obsolete. In special cases it may have some interesting additional functionality. I found this issue comment listing the differences.
I prefer not using the plugin if not specifically needed, because it may have unexpected effects on the resolution result by the way it "forces" all versions of spring-boot-dependencies. But it can be a choice to use the plugin if there is a good reason.
Hi @jjohannes, Thank you for all the effort you have put into this repo and for sharing your knowledge about Gradle through your fantastic compilation of videos on YouTube.
I was reviewing the setup project for Java + Spring Boot that you have shared, and I noticed that the
id("io.spring.dependency-management") version "1.1.4"
plugin, which provides dependency version resolution for all Spring Boot based projects, was not used.I am curious to know why you chose not to use this plugin. I would appreciate it if you could share your thoughts on this matter.
The text was updated successfully, but these errors were encountered: