[MNG-5197] locally declared test dependency's first-generation transitive dependency version incorrectly overrides (n > 1)th-generation compile-scoped dependency version

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.2.1, 3.0.3
• Fix Version/s: needing-scrub-3.4.0-fallout
• Component/s: Dependencies
• Environment: OSX, Windows 7
• Assignee: Unassigned
• Reporter: Matthew Jason Benson
• Created: 09/Nov/11 16:31
• Updated: 25/Mar/17 22:17

Description

This bug seems to relate to MNG-4457, MNG-4156, and potentially others, but I have opened a new issue since nothing I found while searching could be described in precisely the same way.

The test project I am attaching defines three modules:
thing1
thing2
thing3

thing1 depends on hamcrest-core 1.2
thing2 depends on thing1 and junit 4.10
thing3 depends on thing2 and junit 4.10

If you install these, you can then view the dependency trees for thing2 and thing3 and see that thing1 correctly resolves v1.2 for hamcrest-core. thing3, however, apparently overrides the version back to 1.1, apparently accessed transitively via junit.

Thanks to Mark Struberg for his help in isolating this behavior!

Issue Links

• is related to: MNG-3890 Transitive dependencies override explicitly set scope.