maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Hablützel (JIRA) <>
Subject [jira] (MEAR-180) Artifacts with same ID are ignored in packaging
Date Fri, 14 Feb 2014 07:11:57 GMT
Reto Hablützel created MEAR-180:

             Summary: Artifacts with same ID are ignored in packaging
                 Key: MEAR-180
             Project: Maven Ear Plugin
          Issue Type: Bug
    Affects Versions: 2.9
            Reporter: Reto Hablützel

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:

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 \[\] 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

This message was sent by Atlassian JIRA

View raw message