[
http://jira.codehaus.org/browse/MNG-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204222#action_204222
]
Jason van Zyl commented on MNG-2274:
------------------------------------
Provide a test project, these projects are old and too hard to manually track
down. Create a sample project that expresses the problem and reopen.
> error in depth handling of dependency tree
> ------------------------------------------
>
> Key: MNG-2274
> URL: http://jira.codehaus.org/browse/MNG-2274
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Brett Porter
> Fix For: 3.x
>
>
> see r399960 of the assembly plugin for a pom that showed this
> Basically what happened was:
> 1) maven-archiver brought in plexus-archiver which brought in
> plexus-container-default (depth 2)
> 2) plugin-test-harness brought in a newer plexus-container-default (depth 1),
> scope test
> 3) newer one is selected, but changes in 2.0.4 means that it keeps the first
> node and applies the version
> 4) plexus-archiver (newer version) didn't bring in plexus-container-default,
> but previous one is disabled, along with its children
> we can't shift dependencies here - the setting of the version on the farthest
> node should be changed so that the nearest one is selected and any
> dependencies from the farthest one that apply (because of the stronger scope)
> are dragged in.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
