[jira] Work started: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib

["Stephane Nicoll (JIRA)" <ji...@codehaus.org>]

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

Work on MWAR-116 started by Stephane Nicoll.

> The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
> ----------------------------------------------------------------------------
>
>                 Key: MWAR-116
>                 URL: http://jira.codehaus.org/browse/MWAR-116
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-1
>            Reporter: Chris Moesel
>            Assignee: Stephane Nicoll
>         Attachments: mwar_93_webapp.zip
>
>
> I've tried using the new outputFileNameMapping feature (MWAR-93) by adding the following to my POM:
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-war-plugin</artifactId>
>   <version>2.1-alpha-1-SNAPSHOT</version>
>   <configuration>
>     <outputFileNameMapping>${artifactId}.${extension}</outputFileNameMapping>
>   </configuration>
> </plugin>
> This results in really oddly named files in my web-inf/lib now.  A typical example:
> org.springframework-mywebapp.null
> So, the resulting files are really mapped more like: ${groupId of the dependency}-${artifactId of my war module}.null
> I've attached an example Maven 2 project that demonstrates this.  Just run "mvn package" and look at the result in target.

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