[
http://jira.codehaus.org/browse/MNG-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159040#action_159040
]
Benjamin Bentmann commented on MNG-3769:
----------------------------------------
OK, I have traced down my inability to reproduce the reported issue to
inconsistent POMs in my local repo. It appears the two Maven versions have
different preferences with regard to the remote repo being consulted:
a) central:
http://repo1.maven.org/maven2/javax/xml/soap/saaj-api/1.3/saaj-api-1.3.pom
b) java.net:
http://download.java.net/maven/1/javax.xml.soap/poms/saaj-api-1.3.pom
Note the different dependency sections in these POMs. It requires the POM from
central to reproduce the issue.
> [regression] Excluding relocated transitive dependencies does not work
> ----------------------------------------------------------------------
>
> Key: MNG-3769
> URL: http://jira.codehaus.org/browse/MNG-3769
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.1.0-M1
> Reporter: Dirk Olmes
> Priority: Blocker
> Fix For: 2.0.10, 2.1.0-M2
>
> Attachments: MNG-3769-debugging-info-2.zip,
> MNG-3769-debugging-info.zip, mng-3769.txt, pom.xml
>
>
> I'm trying to exclude transitive dependencies of a dependency. This works
> fine with 2.0.9, however it does not work with 2.1.0-M1.
> Run {{mvn dependency:tree}} on the attached pom.xml with 2.0.9 and note how
> there is no javax.activation in the tree. Re-run with 2.1.0-M1 and note how
> javax.activation shows up in the dependencies tree.
--
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
