[MNG-6141] Dependency management overrides are not transitive and should be considered an anti-pattern.

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Fix Version/s: 4.x / Backlog
• Assignee: Unassigned
• Reporter: Christian Schulte
• Created: 29/Dec/16 18:55
• Updated: 14/Jan/19 00:28

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.

Issue Links

• is blocked by: MRESOLVER-33 New 'DefaultDependencyManager' managing dependencies on all levels supporting transitive dependency management