Ian Phipps created MNG-5273:
-------------------------------
Summary: Transitive dependencies with scope provided ending up in
the final artifact
Key: MNG-5273
URL: https://jira.codehaus.org/browse/MNG-5273
Project: Maven 2 & 3
Issue Type: Bug
Components: Dependencies
Affects Versions: 3.0.4, 3.0.3
Environment: Windows 7, Sun OS 5.1
Reporter: Ian Phipps
Marking jaxws-rt as a provided dependency:
{noformat}<dependency>
<groupId>com.sun.xml.ws</groupId>
<artifactId>jaxws-rt</artifactId>
<version>2.1.4</version>
<scope>provided</scope>
</dependency>{noformat}
Correctly resolves jaxb-impl as a provided dependency (dependency:tree output
from 3.0.3 and 3.0.4):
{noformat}[INFO] +- com.sun.xml.ws:jaxws-rt:jar:2.1.4:provided
[INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.1.7:provided
[INFO] | +- com.sun.xml.stream.buffer:streambuffer:jar:0.7:provided
[INFO] | +- com.sun.xml.stream:sjsxp:jar:1.0.1:provided
[INFO] | +- org.jvnet.staxex:stax-ex:jar:1.2:provided
[INFO] | +- com.sun.org.apache.xml.internal:resolver:jar:20050927:provided
[INFO] | \- org.jvnet:mimepull:jar:1.2:provided {noformat}
But for some reason, in Maven 3 (tried 3.0.3 and 3.0.4), using a packaging type
of "war", jaxb-impl-2.1.7 ends up in the final artifact.
It is correctly omitted from the final artifact in maven 2.x.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
