[MEAR-180] Artifacts with same artifactId/version are ignored in packaging

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9
• Fix Version/s: 2.10
• Assignee: Karl Heinz Marbaise
• Reporter: Reto Hablützel
• Created: 14/Feb/14 01:10
• Updated: 19/Feb/15 05:44
• Resolved: 03/Nov/14 14:52

Description

The attached sample consists of an ear that references two other projects, both of which have the same artifactId and the same versionId, but not the same groupId.

Both are to be packaged in the lib folder, but only the first will make it in, because the maven ear plugin identifies them only by their artifactId and version. This means that when it sees the second dependency, it thinks it was already in there.

Note that I already brought this up on the mailing list: https://mail-archives.apache.org/mod_mbox/maven-users/201402.mbox/browser

Follow these steps to recreate the issue based on the attached sample:

Install 'utilities' project in 'collections':
collections/utilities> mvn install

Install 'utilities' project in 'email':
email/utilities> mvn install

Package 'ear' project:
ear> mvn package

Look at contents of ear and notice how only one jar is included:
ear> unzip -v target/ear-1.0.0.ear

Now use the debug flag to see why only one gets included:
ear> mvn --debug clean package

Partial output:
[INFO] Copying artifact [jar:ch.rethab.email:utilities:1.0.0] to [utilities-1.0.0.jar]
[DEBUG] Skipping artifact [jar:ch.rethab.collections:utilities:1.0.0], as it is already up to date at [utilities-1.0.0.jar]

Note that this sample shows how dependent libraries are ignored, but I think it is also an issue if you have two ejbs with the same name and version - though that is probably far less likely.