[MNG-3038] Transitive DepMan not working (per MNG-1577) [use case attached]

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 2.0.5, 2.0.6
• Component/s: Artifacts and Repositories
• Assignee: Patrick Schneider
• Reporter: Joakim Erdfelt
• Created: 06/Jun/07 11:23
• Updated: 02/Jul/14 08:44
• Resolved: 11/Jun/14 22:38

Description

When working with the example use case described by Carlos on the MNG-1577 thread.
http://www.nabble.com/Re%3A--vote--MNG-1577-as-the-default-behavior-p9506667s177.html

What about this use case for transitive dependencyManagement? has been tested?

A -> B -> C -> D

C depends on D 1.0
B has D 2.0 in dependencyManagement, no D in dependencies

A should get D 2.0 

It was discovered that this does not work.
Sample Project / Use Case is attached. (655 bytes)

Issue Links

• is duplicated by: MNG-4821 Wrong spring-context version resolved when depending on artifact with dependency management and jersey-spring dependency
• relates to: MNG-1577 dependencyManagement does not work for transitive dependencies