[
https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte updated MNG-6141:
-----------------------------------
Description:
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.
was:
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.
> 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'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)
