So when the java-cfenv library migrated to Gradle, the project began to use a Gradle platform for version alignment. The chosen platform was the spring-boot-dependencies BOM. While the java-cfenv-{version}.pom does not include any <dependencyManagement> section, the java-cfenv-{version}.module includes the platform constraint. When the library is used with a Spring project that is not aligned with the spring-boot-dependencies BOM platform that the project is using this results in Gradle changing the project's dependencies through it's dependency constraint in the module metadata.
The associated changes on this PR, removes the Spring Boot Dependencies BOM and instead uses the aligned Jackson BOM that is used for the current Spring Boot version. Then then changes the dependency constraint such that it will now only effect the Jackson modules, instead of a much, much larger set of dependencies.
anthonydahanne
commented
1 year ago
So when the
java-cfenvlibrary migrated to Gradle, the project began to use a Gradle platform for version alignment. The chosen platform was thespring-boot-dependenciesBOM. While thejava-cfenv-{version}.pomdoes not include any<dependencyManagement>section, thejava-cfenv-{version}.moduleincludes the platform constraint. When the library is used with a Spring project that is not aligned with thespring-boot-dependenciesBOM platform that the project is using this results in Gradle changing the project's dependencies through it's dependency constraint in the module metadata.The associated changes on this PR, removes the Spring Boot Dependencies BOM and instead uses the aligned Jackson BOM that is used for the current Spring Boot version. Then then changes the dependency constraint such that it will now only effect the Jackson modules, instead of a much, much larger set of dependencies.