[
https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786367#comment-15786367
]
Joerg Schaible commented on MNG-6141:
-------------------------------------
Sorry, but this is a perfectly legal situation! We manage a global POM with
depMgmt section for some products. However, some derived projects will override
the settings in the depMgmt section on purpose. Yes, it is possible to shoot
yourself into the foot using a depMgmt section, but in any case, it must have
been my own decision. Nobody said, the managing dependencies is easy, but I
expect the build tool to respect my choices.
> 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)
