[jira] Commented: (MWAR-80) Classifier in jar file name is removed once assembled into war file

["Piotr Tabor (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MWAR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90281 ] 

Piotr Tabor commented on MWAR-80:
---------------------------------

It is still true. 
When configuration is: 
"
 <artifactId>zzz</artifactId>
 ...
 <configuration>
     <classifier>fine</classifies>
     <archiveClasses>true</archiveClasses>
 </configuration>

as a result we will get: 
    zzz-fine.war
but also: *zzz-fine.war/WEB-INF/lib/zzz.jar*

It is probably "by design". 

So I think that there are two possibilities:
a)   to add to documentation comment about it and close the bug
b)   to add new parameter - for example <achiveClassesClassifier>bad<achiveClassesClassifier>
which will create: *zzz-fine.war/WEB-INF/lib/zzz-bad.jar*. 

If it's useful (actually I don't see any use case for that stuff), I can prepare a patch. 





> Classifier in jar file name is removed once assembled into war file
> -------------------------------------------------------------------
>
>                 Key: MWAR-80
>                 URL: http://jira.codehaus.org/browse/MWAR-80
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>         Environment: Maven 2.0.4, JDK 1.5, maven-war-plugin version 2.0
>            Reporter: Andreas Guther
>
> We use the Maven classifier to distinguish between different jar files of the same version build for different purposes.  An example would be the classifier used for TestNG to distinguish between jdk15 and jdk14 jar files.
> I noticed that the jar file (for example test-1.0-classifier.jar) ends up in the WEB-INF/lib folder with the classifier removed (i.e. following the example test.1.0.jar).
> This is unexpected and confusing.  Since there is very little documentation about the expected behavior while using classifiers, it is not clear if this is intenionally or a bug.  
> If intenionally, it should be mentioned in the maven-war-plugin documentation.  Maybe in that case it would be an enhancement to configure if the classifier should be preserved or removed.
> However, the current behavior is undocumented and unexpected.

-- 
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