Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.1-alpha-2
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:jdk 1.6 - maven 2.0.9
-
Number of attachments :
Description
I have a parent pom which defines a build number using the build number plugin. My project's finalName is of the form :
$
_$
{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)
-
Activity
Hugues Narjoux
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Attachment | parent_pom.xml [ 39990 ] |
Stéphane Nicoll
made changes -
Stéphane Nicoll
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Assignee | Stephane Nicoll [ sni ] | |
| Resolution | Duplicate [ 3 ] |
Can you give us a POM that shows the configurations needed to reproduce this?