[
https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267225#comment-16267225
]
Curtis Rueden edited comment on MNG-6141 at 11/27/17 6:41 PM:
--------------------------------------------------------------
It would be a shame indeed for that work to be lost. But my understanding was
that these patches were going to be cherry-picked into future releases, no?
was (Author: ctrueden):
It would be a shame indeed for that work to be lost. But my understanding is
that these patches were going to be cherry-picked into future releases, no?
> 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-3.zip, MNG-6141.zip
>
>
> Overriding the dependency management in a module's {{<dependencies>}}
> section, 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 from inside a {{<dependencies>}} element 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 that way without noticing this is not supported transitively.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
