[
http://jira.codehaus.org/browse/MSHADE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190014#action_190014
]
Paul Hammant commented on MSHADE-62:
------------------------------------
You're right Ben, the following was what I wanted ...
{noformat}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<version>1.2.1</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>shade</goal>
</goals>
<configuration>
<shadedArtifactId>picocontainer</shadedArtifactId>
<filters>
<filter>
<artifact>com.thoughtworks.paranamer:paranamer</artifact>
<excludes>
<exclude>com/thoughtworks/paranamer/Javadoc*</exclude>
</excludes>
</filter>
</filters>
<relocations>
<relocation>
<pattern>com.thoughtworks.paranamer</pattern>
<shadedPattern>org.picocontainer.paranamer</shadedPattern>
</relocation>
</relocations>
</configuration>
</execution>
</executions>
</plugin>
{noformat}
This bug can be closed - sorry for wasting your time
> We need an <obliterate/> element - to TRULY exclude classes from resulting
> jar
> -------------------------------------------------------------------------------
>
> Key: MSHADE-62
> URL: http://jira.codehaus.org/browse/MSHADE-62
> Project: Maven 2.x Shade Plugin
> Issue Type: New Feature
> Reporter: Paul Hammant
>
> 'exclusions' is misnamed - it should be 'leaveAsIs' or somesuch.
> I want to totally exclude some packages or classes from the resulting jar.
> As in leave them out, or kill them, or don't have them at all in the
> resulting jar. Neither as their original class name nor their potential new
> class name.
> Perforce has an 'obliterate' concept, given exclude is already used in shade,
> maybe obliterate is the new element for this essential feature.
--
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
