[
http://jira.codehaus.org/browse/MWAR-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165293#action_165293
]
Dennis Lundberg commented on MWAR-176:
--------------------------------------
Can you give us a POM that shows the configurations needed to reproduce this?
> when archiveClasses is true, jar file has incorrect name
> --------------------------------------------------------
>
> Key: MWAR-176
> URL: http://jira.codehaus.org/browse/MWAR-176
> Project: Maven 2.x War Plugin
> Issue Type: Bug
> Affects Versions: 2.1-alpha-2
> Environment: jdk 1.6 - maven 2.0.9
> Reporter: Hugues Narjoux
>
> I have a parent pom which defines a build number using the build number
> plugin. My project's finalName is of the form :
> ${artifcatId}_${version}_${buildNumber}
> The war is correctly named, but the when using archiveClasses the jar is not
> named properly: it is named the same but without replacing the buildNumber
> property, e.g:
> "myAtifcat_1.0_${buildNumber}.jar"
> It works fine if the build number is defined in the pom itself. This happens
> if the buidlNumber is defined in a parent pom.
--
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
