Right now the root pom.xml has at least 2 responsibilities:
- versions management
- default plugins configurations, which are supposed to be inherited by child sub-modules
IMO it would be great if versions could be managed in a dedicated place (like Gradle's libs.versions.toml version catalog or Gradle's java-platform POM)
Such separation of responsibilities can be achieved in Maven if the root pom.xml will extend from some versions-management-pom.xml. This way all versions will get managed in one single place, which will declutter the root pom.xml
@johanhaleby what do you think? I am only afraid this can potentially break automatic dependency upgrades (from tools like Renovate or dependabot), but I can't say for sure, this needs to be tested.
Right now the root
pom.xmlhas at least 2 responsibilities:IMO it would be great if versions could be managed in a dedicated place (like Gradle's
libs.versions.tomlversion catalog or Gradle'sjava-platformPOM)Such separation of responsibilities can be achieved in Maven if the root
pom.xmlwill extend from someversions-management-pom.xml. This way all versions will get managed in one single place, which will declutter the root pom.xml@johanhaleby what do you think? I am only afraid this can potentially break automatic dependency upgrades (from tools like Renovate or dependabot), but I can't say for sure, this needs to be tested.