What is currently missing?
We currently define quite a few <properties>, and context in <dependencyManagement> and <pluginManagement> in the parent pom, then proceed to override or ignore them in the child pom. This makes it difficult to review what is happening in version bumps.
For example, there's really no need to manage all the google dependencies via the bom in the parent pom if they are introduce in this module, or to define commons.lang3.version> in the parent pom if we're not going to put the dependency in the parent <dependencyManagement>. This applies even more when we override it here in the child module.
Likewise with other context from the parent pom that is repeated throughout other modules like <releaseManagement> and <profiles>.
How could this be improved?
Define dependencies and versions where they are introduced into the module.
Trim repeated elements from child poms.
Is this a feature you would work on yourself?
What is currently missing?
We currently define quite a few
<properties>, and context in<dependencyManagement>and<pluginManagement>in the parent pom, then proceed to override or ignore them in the child pom. This makes it difficult to review what is happening in version bumps.For example, there's really no need to manage all the google dependencies via the bom in the parent pom if they are introduce in this module, or to define
commons.lang3.version>in the parent pom if we're not going to put the dependency in the parent<dependencyManagement>. This applies even more when we override it here in the child module.Likewise with other context from the parent pom that is repeated throughout other modules like
<releaseManagement>and<profiles>.How could this be improved?
Define dependencies and versions where they are introduced into the module.
Trim repeated elements from child poms.
Is this a feature you would work on yourself?