[
http://jira.codehaus.org/browse/MNG-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirk Olmes updated MNG-3007:
----------------------------
Attachment: pom.xml
I'm attaching a pom that can be used to demo the issue. Run it with an empty
repo, once without any profiles activated and once with the codehaus profile.
Output of dependency:tree when dependencies are resolved from central only:
{code}
[INFO] [dependency:tree]
[INFO] org.mule:MNG-3007:jar:1.0-SNAPSHOT
[INFO] \- org.codehaus.xfire:xfire-core:jar:1.2.6:compile
[INFO] +- javax.activation:activation:jar:1.1:compile
[INFO] +- javax.mail:mail:jar:1.4:compile
[INFO] +- wsdl4j:wsdl4j:jar:1.6.1:compile
[INFO] +- jaxen:jaxen:jar:1.1-beta-9:compile
[INFO] | +- xerces:xmlParserAPIs:jar:2.6.2:compile
[INFO] | \- xerces:xercesImpl:jar:2.6.2:compile
[INFO] +- stax:stax-api:jar:1.0.1:compile
[INFO] +- commons-codec:commons-codec:jar:1.3:compile
[INFO] +- org.apache.ws.commons:XmlSchema:jar:1.1:compile
[INFO] +- org.codehaus.woodstox:wstx-asl:jar:3.2.0:compile
[INFO] +- jdom:jdom:jar:1.0:compile
[INFO] +- commons-logging:commons-logging:jar:1.0.4:compile
[INFO] \- commons-httpclient:commons-httpclient:jar:3.0:compile
[INFO] \- junit:junit:jar:3.8.1:compile
{code}
Output of dependency:tree when dependencies are resolved from codehaus (legacy
layout) and from central:
{code}
[INFO] org.mule:MNG-3007:jar:1.0-SNAPSHOT
[INFO] \- org.codehaus.xfire:xfire-core:jar:1.2.6:compile
[INFO] +- javax.activation:activation:jar:1.1:compile
[INFO] +- javax.mail:mail:jar:1.4:compile
[INFO] +- wsdl4j:wsdl4j:jar:1.6.1:compile
[INFO] +- jaxen:jaxen:jar:1.1-beta-9:compile
[INFO] +- stax:stax-api:jar:1.0.1:compile
[INFO] +- commons-codec:commons-codec:jar:1.3:compile
[INFO] +- org.apache.ws.commons:XmlSchema:jar:1.1:compile
[INFO] +- org.codehaus.woodstox:wstx-asl:jar:3.2.0:compile
[INFO] +- jdom:jdom:jar:1.0:compile
[INFO] +- commons-logging:commons-logging:jar:1.0.4:compile
[INFO] \- commons-httpclient:commons-httpclient:jar:3.0:compile
[INFO] \- junit:junit:jar:3.8.1:compile
{code}
Note how jaxen has transitive dependencies in the first case and how it hasn't
in the second case. While both poms differ, they share the ones that appear as
transitive dependencies of jaxen in the first case above.
> 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
>
> Attachments: pom.xml
>
>
> 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
