[jira] Updated: (MNG-3007) Resolving legacy dependency ignores transitive dependencies

["Brian Fox (JIRA)" <ji...@codehaus.org>]

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

Brian Fox updated MNG-3007:
---------------------------

    Fix Version/s:     (was: Reviewed Pending Version Assignment)
                   2.0.x

can we get a sample project?

> Resolving legacy dependency ignores transitive dependencies
> -----------------------------------------------------------
>
>                 Key: MNG-3007
>                 URL: http://jira.codehaus.org/browse/MNG-3007
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.6
>            Reporter: Dirk Olmes
>             Fix For: 2.0.x
>
>
> Trying to resolve a dependency from a repo with legacy layout (dist.codehaus.org) seems to ignore this dependency's transitive dependencies.
> I stumbled over this issue while building mule: the xfire module depends on jaxen which is available from dist.codehaus.org (legacy layout) and from central (m2 repo layout). For xfire we need to have dist.codehaus.org in the pom.
> When pulling jaxen from the legacy layout all transitive dependencies, although declared in the legacy pom, will not be included in this module's dependencies. If I happen to have jaxen already fetched from central into my local repo, the transitive dependencies will show up, causing the entire build to fail.
> IMHO the dependency resolution of m1 poms should consider that artifact's transitive dependencies as it is the case with m2 poms.

-- 
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