You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2014/07/02 15:45:14 UTC

[jira] (MNG-2274) error in depth handling of dependency tree

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

Paul Benedict updated MNG-2274:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> error in depth handling of dependency tree
> ------------------------------------------
>
>                 Key: MNG-2274
>                 URL: https://jira.codehaus.org/browse/MNG-2274
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.4
>            Reporter: Brett Porter
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)