[ https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214155#comment-16214155 ]
Christian Schulte commented on MNG-6141: ---------------------------------------- [~joehni] To not introduce any misunderstandings. This issue is about overriding dependency management locally within a module's {{<dependencies>}} section. Such overrides are only in effect locally during building the module and nowhere else - not even in the same reactor. See the attached example project. You could override the dependency management inside {{<dependencyManagement>}} in a consistent way, though. > Dependency management overrides are not transitive and should be considered > an anti-pattern. > -------------------------------------------------------------------------------------------- > > Key: MNG-6141 > URL: https://issues.apache.org/jira/browse/MNG-6141 > Project: Maven > Issue Type: Bug > Reporter: Christian Schulte > Priority: Critical > Attachments: MNG-6141.zip > > > Overriding the dependency management in a module, the overridden value will > not be preserved transitively. It makes no sense to be able to override the > dependency management in a module if that is only effective in that module > and nowhere else. Overriding the dependency management should be considered > an anti-pattern. Maven should provide a warning when it is used. During the > development of Maven 3.4, there have been quite a few discussions on dev@ > about build issues which were all caused by overriding the dependency > management without noticing this is not supported transitively. -- This message was sent by Atlassian JIRA (v6.4.14#64029)