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

["Christian Schulte (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schulte resolved MNG-5197.
------------------------------------
    Resolution: Fixed
      Assignee: Christian Schulte  (was: Jason van Zyl)

> locally declared test dependency's first-generation transitive dependency version incorrectly overrides (n > 1)th-generation compile-scoped dependency version
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-5197
>                 URL: https://issues.apache.org/jira/browse/MNG-5197
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.2.1, 3.0.3
>         Environment: OSX, Windows 7
>            Reporter: Matt Benson
>            Assignee: Christian Schulte
>             Fix For: 3.5.0
>
>         Attachments: test-versions.tar.gz
>
>
> 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!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)