[jira] Updated: (MWAR-112) The package RELEASE version of jar files are named jarname-RELEASE.jar

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MWAR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MWAR-112:
---------------------------------

    Attachment: MWAR-112.zip

Attaching a project that shows that this is not a problem. I tried with versions 2.0.2, 2.1-alpha-1 and 2.1-alpha-2.

> The package RELEASE version of jar files are named jarname-RELEASE.jar
> ----------------------------------------------------------------------
>
>                 Key: MWAR-112
>                 URL: http://jira.codehaus.org/browse/MWAR-112
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>         Environment: Maven version: 2.0.7
> Java version: 1.5.0_11
> OS name: "windows xp" version: "5.1" arch: "x86"
>            Reporter: Chandra Patni
>            Priority: Minor
>         Attachments: MWAR-112.zip
>
>
> Suppose, I have dependency
>     <dependency>
>       <groupId>mygroup</groupId>
>       <artifactId>mylib</artifactId>
>       <version>RELEASE</version>
>     </dependency>
> In a war packaging, if I run mvn package, the war file contains mylib-RELEASE.jar
> Similarly, if you run mvn clean compile war:exploded, the exploded dir contains mylib-RELEASE.jar
> It packages dereferenced value of RELEASE if I do,
> mvn clean compile
> mvn war:exploded

-- 
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