Maven 2.x WAR Plugin

when archiveClasses is true, jar file has incorrect name

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major 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 :
    1

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

Improvement - An improvement or enhancement to an existing feature or task. MWAR-215 class file JAR inconsistency (archiveClasses and attachClasses options)

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

People

  • Assignee:
    Stéphane Nicoll
    Reporter:
    Hugues Narjoux
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: