maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MSHADE-62) We need an <obliterate/> element - to TRULY exclude classes from resulting jar
Date Sun, 06 Sep 2009 16:09:31 GMT

    [ http://jira.codehaus.org/browse/MSHADE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190010#action_190010
] 

Benjamin Bentmann commented on MSHADE-62:
-----------------------------------------

Paul, can you be more specific why the "fine-grained control of which classes from the selected
dependencies are included" from the example [Selecting Contents for Uber JAR|http://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html]
does not work?

> 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

        

Mime
View raw message