Is there any reason to use the dependency management section in a child pom? I'm looking at a maven project in my organization that uses inheritance and aggregation, where the parent and child poms both have a dependency management section. Is the child one doing anything?

I found this question really helpful but didn't find the answer to my specific question - Differences between dependencyManagement and dependencies in Maven

CodePudding user response：

It can be used to control the version of transitive dependencies (libraries that your direct dependencies depend on) without adding a direct dependency.

CodePudding user response：

Child POM will add or override dependency management entries of the parent POM.

Keep in mind that you really, really don't want to have different versions of the same dependency in your codebase. So use this feature judiciously. Preferably you should have organization-wide parent POM file with all dependency versions defined and child POMs don't change them.