[MWAR-116] The outputFileNameMapping config creates bad dependency files in WEB-INF/lib

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1-alpha-1
• Fix Version/s: 2.1-alpha-2
• Assignee: Olivier Lamy
• Reporter: Chris Moesel
• Created: 11/Sep/07 16:18
• Updated: 01/Aug/08 07:53
• Resolved: 30/Jan/08 17:16

Description

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.