[MWAR-176] when archiveClasses is true, jar file has incorrect name

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.1-alpha-2
• Environment: jdk 1.6 - maven 2.0.9
• Assignee: Stephane Nicoll
• Reporter: Hugues Narjoux
• Created: 27/Nov/08 03:07
• Updated: 07/Apr/15 18:37
• Resolved: 16/Aug/10 01:46

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.

Issue Links

• is duplicated by: MWAR-215 class file JAR inconsistency (archiveClasses and attachClasses options)