[
http://jira.codehaus.org/browse/MSHADE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MSHADE-55:
------------------------------------
Attachment: pom.xml
Demo project based on your descriptions. It has a direct dependency on
junit:3.8.1 whereas its other dependency plexus-container-default has a
transitive dependency on junit:3.8.2. Maven correctly resolves this conflict to
use the nearer junit:3.8.1 and the Shade Plugin properly packages all contents
of the junit.jar, e.g. {{junit/runner/excluded.properties}}.
The resolution of the dependency conflict is transparent to the Shade Plugin
(or any other plugin) and by itself can't have an effect on its operation. If a
file is missing from the shaded JAR, it's either not readable from any input
JAR or excluded by configuration.
> dependency conflict causes only .class files included in jar, not .properties
> -----------------------------------------------------------------------------
>
> Key: MSHADE-55
> URL: http://jira.codehaus.org/browse/MSHADE-55
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.2.1
> Environment: Maven 2.0.9, Windows
> Reporter: rick gordon
> Priority: Minor
> Attachments: pom.xml
>
>
> My pom had a direct dependency on one version of a jar (3.3.5), but several
> of the transitive dependencies had a dependency on a later version (3.3.6).
> Looking at maven debug output (-X) I could see that it was choosing the 3.3.5
> version because it was 'nearer' than the the 3.3.6 version. But when
> including it, it would only include the .class files and skip a .properties
> file in it. Switching the original dependency to the newer version (3.3.6)
> 'fixed' the problem, so that the .properties file was now included.
--
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
