You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/01/17 14:35:56 UTC
[jira] Closed: (MSHADE-72) Classes from current artifact are
excluded when explicit shaded includes are provided
[ http://jira.codehaus.org/browse/MSHADE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MSHADE-72.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.1
Assignee: Benjamin Bentmann
Fixed in [r900138|http://svn.apache.org/viewvc?view=revision&revision=900138].
> Classes from current artifact are excluded when explicit shaded includes are provided
> -------------------------------------------------------------------------------------
>
> Key: MSHADE-72
> URL: http://jira.codehaus.org/browse/MSHADE-72
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Linux; maven 2.0.9
> Reporter: Mat Johns
> Assignee: Benjamin Bentmann
> Fix For: 1.3.1
>
> Attachments: example.zip
>
>
> When specifying artifacts to include in shaded jar, the final jar seem to exclude the built classes for the current artifact. This is a change from 1.2.2 where the current artifact was (quite rightly) included (as you are not really shading it, but rather others into it).
> Please find attached an example of this behaviour (example.zip);
> $ mvn -DshadePlugin=1.2.2 clean package
> $ unzip -l two/target/two-1-SNAPSHOT.jar | grep class
> 260 01-11-10 18:37 org/test/two/Two.class
> 317 01-11-10 18:37 shaded/org/test/one/One.class
> $ mvn -DshadePlugin=1.3 clean package
> $ unzip -l two/target/two-1-SNAPSHOT.jar | grep class
> 317 01-11-10 18:41 shaded/org/test/one/One.class
--
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