[MWAR-7] Referenced projects' artifacts naming scheme behaves differently when ran from reactor

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0
• Environment: maven-war-plugin versions 2.0-beta-1 and 2.0-beta-2
• Assignee: Maria Odea B. Ching
• Reporter: Cédric Vidal
• Created: 12/Dec/05 12:18
• Updated: 21/Jul/09 04:47
• Resolved: 24/Mar/06 00:50

Description

When running mvn install from a war packaged project, the referenced projects' artifacts are bundled into the WEB-INF/lib directory with the following naming scheme ${groupId}${artifactId}${version}.jar, but when running mvn install as part of the reactor, the referenced projects' artifacts are bundled into the WEB-INF/lib directory with the following naming scheme ${pom.build.finalName}.jar

The naming scheme should be the same in the two situations for the sake of consistency, but also to avoid the disturbing (for the end user) situation where you end up having the same dependencies present twice with different names.

Issue Links

• is related to: MNG-2045 Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
• is related to: MNG-4248 CLONE -Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)