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 artifactId/version are ignored in packaging
Date Thu, 19 Feb 2015 09:00:19 GMT


Reto Hablützel commented on MEAR-180:

As far as the _duplicate artifacts are silently ignored and the mave-ear-plugin doesn't even
warn about it_ is concerned, I wouldn't say this issue has been resolved as of version 2.10.
I understand you added a flag, however once you know you might have a problem in that area,
you might as well fix it right away instead of enabling the flag. My issue is that the plugin
silently ignoes it by default - it doesn't even warn.

But then I understand you're going to move to fully qualified names with the next major version
and I appreciate your efforts.

\- Reto

> Artifacts with same artifactId/version are ignored in packaging
> ---------------------------------------------------------------
>                 Key: MEAR-180
>                 URL:
>             Project: Maven Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.9
>            Reporter: Reto Hablützel
>            Assignee: Karl-Heinz Marbaise
>             Fix For: 2.10
>         Attachments:
> 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:
> {quote}
> 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\]
> {quote}
> 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.

This message was sent by Atlassian JIRA

View raw message