You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joerg Schaible (JIRA)" <ji...@apache.org> on 2016/05/19 15:32:13 UTC

[jira] [Commented] (MJAR-224) Not possible to exclude classes from primary jar only

    [ https://issues.apache.org/jira/browse/MJAR-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291301#comment-15291301 ] 

Joerg Schaible commented on MJAR-224:
-------------------------------------

This is the normal behaviour.  A plugin configuration applies for every execution. You may overwrite specific parts with individual configuration blocks for an execution. The default execution has the id "default" (IIRC). You have to declare it explicitly if you want to set configuration stuff that should not apply to other executions.

> Not possible to exclude classes from primary jar only
> -----------------------------------------------------
>
>                 Key: MJAR-224
>                 URL: https://issues.apache.org/jira/browse/MJAR-224
>             Project: Maven JAR Plugin
>          Issue Type: Bug
>            Reporter: Sebb
>
> The <excludes> config item can be used to exclude classes from a jar.
> However, if this is done for the main jar, the exclusion also applies to any other jars created with a different classifier.
> It does not appear to be possible to exclude a class from the main jar and include it in any others.
> This forces the use of other solutions such a the Maven Antrun Plugin



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)