[
https://jira.codehaus.org/browse/MWAR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309731#comment-309731
]
Dennis Lundberg commented on MWAR-256:
--------------------------------------
Rafal,
You really do need to split the module in two for your use case. If other
projects are interested in the JAR, then that JAR should be in a separate
module. That is the Maven convention.
> it's not possible to create classes attachment without classifier
> -----------------------------------------------------------------
>
> Key: MWAR-256
> URL: https://jira.codehaus.org/browse/MWAR-256
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
> Affects Versions: 2.1.1
> Reporter: Rafal Krzewski
>
> I would like to package classes in my war-packaged project into a jar, but I
> don't want to use default 'classes' classifier assigned by the plugin. The
> generated artifacts have distinct packaging types, so there is no conflict
> and the classifier provides no useful additional information. Using the
> following configuration:
> {quote}
> {{<configuration>}}
> {{<classesClassifier/>}}
> {{</configuration>}}
> {quote}
> Results in "classes" classifier being used anyway. If I understand the
> behavior correctly Plexus assigns the variable it's default value, when
> presented an empty input. I don't think this can be fixed in way that is both
> clean and backward compatible. Either the default value will change, which
> would break existing builds that don't specify plugin version explicitly, or
> some clunky additional parameter like
> {{<useClassesClassifier>false</useClassesClassifier>}}, or magic value like
> {{<classesClassifier>NONE</classesClassifier>}} need to be introduced.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
