This message was deleted.
# community-supports
Slackbot
03/06/2023, 2:39 PMThis message was deleted.
m
melix
03/06/2023, 2:45 PMProbably because you are using the Spring DM plugin
melix
03/06/2023, 2:46 PMYou should remove it and use Gradle's built-in support for platforms (BOMs)
v
Vampire
03/06/2023, 3:36 PMWhich is even recommended by the maintainer of the Spring Dependency Management Plugin.
j
jonnyzzz
03/06/2023, 3:56 PMNice! Let me try that! Thanks
jonnyzzz
03/06/2023, 3:57 PMIs there a standard way to add assertions to the actual class path of a project in Gradle?
v
Vampire
03/06/2023, 4:00 PMWhat do you mean?
m
melix
03/06/2023, 4:00 PMI guess something like this:
Copy code
configurations.runtimeClasspath.incoming.afterResolve {
// whatever you want to check
}👍 1
j
jonnyzzz
03/07/2023, 9:04 AMTested: Gradle's native BOM support solves the problem. More observations: SpringBoot documentation does not clearly recommends to avoid using their plugin. "io.spring.dependency-management" plugin is generated in a fresh project via SpringInitializr.
jonnyzzz
03/07/2023, 9:07 AMThanks Cédric, I will use that approach.
The reasoning behind - we have multiple modules with hundreds of transitive dependencies plus dependency resolution. I'm looking to make the whole process more predictable to catch sudden changes to the classpath. A butterfly effect
v
Vampire
03/07/2023, 2:17 PMYou are right with your observations.
I didn't say the docs or tools recommend it.
I said the maintainer of that plugin recommends it: https://linen.dev/s/gradle-community/t/2579116/what-is-the-proper-way-to-apply-a-bom-in-a-library-project-i#a7d4a60a-ab60-48dc-8477-f3f4462d1e6a :-)
Well, their docs at least say that you get faster builds with the built-in BOM support: https://docs.spring.io/spring-boot/docs/3.0.4/gradle-plugin/reference/htmlsingle/#managing-dependencies
👍 1
6 Views