Playing necromancer here, I still would strongly suggest adding a
"groovy-bom" or "groovy-platform" module,
as even gradle implemented support for platform boms
https://docs.gradle.org/current/userguide/java_platform_plugin.html
I hope we can get this for 3.0 final, and maybe even backported to
e
Moving from the `dependencies` to `dependencyManagement` block is not
semantically equivalent. In the `dependencies` block you get all the
dependencies transitively, meaning that if you request groovy-all, you'd
get all the individual modules. If it's moved to ``
then you only get _recommendations_
Hi,
as I said, it needs to be in the dependencyManagement section, to be
importable into the dependencyManagement of another pom.
You can add groovy-all to dependencyManagement, but that only affects
the version of the artifact itself not the version of its transitive
dependencies, which can be af
On 17.09.2018 02:44, Leonard Brünings wrote:
Hi,
the switch to fine grained artifacts with groovy-2.5 made it harder to
consistently mange package versions.
Many projects offer a bom pom
(https://www.baeldung.com/spring-maven-bom), that manages all the
packages so users of maven have to jus
