[
https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15787962#comment-15787962
]
Christian Schulte commented on MNG-6141:
----------------------------------------
Can you please test if your dependency management is still working the same way
with a recent 3.4.0-SNAPSHOT.
<https://builds.apache.org/view/Maven/job/maven-master-release-status-build/>
That snapshot contains a fix for MNG-5761. As long as you never add a
dependency to something which has overridden the management, nothing should
have changed. I fear those overrides stop working the way you are used to as
soon as they become transitive dependencies somewhere. With this fix, Maven no
longer ignores the transitive dependency management. That leads to the
management overriding those overrides consistently also cross-reactor (issue
described above).
> 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
> Assignee: 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.3.4#6332)
