maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6141) Dependency management overrides are not transitive and should be considered an anti-pattern.
Date Fri, 30 Dec 2016 11:42:58 GMT

    [ https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15787514#comment-15787514
] 

Joerg Schaible commented on MNG-6141:
-------------------------------------

I know, but if you set such defaults in a parent, you may deliberately overwrite it in a child.
At least we do this in some special cases.

> 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)

Mime
View raw message