Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
2.1-alpha-2
-
None
-
None
-
None
-
jdk 1.6 - maven 2.0.9
Description
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.
Attachments
Attachments
Issue Links
- is duplicated by
-
MWAR-215 class file JAR inconsistency (archiveClasses and attachClasses options)
- Closed