[ http://jira.codehaus.org/browse/MWAR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MWAR-80. ------------------------------- Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.1 I have documented the current behavior better. I also added a test case to verify that the classifier of a dependency is not lost in translation. > 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 > Assignee: Dennis Lundberg > Fix For: 2.1 > > > 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