Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Thu, 19 Feb 2015 05:45:18 -0600 (CST)
From: "Karl-Heinz Marbaise (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: 
 <JIRA.152010.1392361858438.19005.1424346318274@codehaus01.managed.contegix.com>
In-Reply-To: <JIRA.152010.1392361858438@codehaus01.managed.contegix.com>
References: <JIRA.152010.1392361858438@codehaus01.managed.contegix.com>
Subject: [jira] (MEAR-180) Artifacts with same artifactId/version are
 ignored in packaging
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


    [ https://jira.codehaus.org/browse/MEAR-180?page=3Dcom.atlassian.jira.p=
lugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D363605#comm=
ent-363605 ]=20

Karl-Heinz Marbaise commented on MEAR-180:
------------------------------------------

Hi Reto, if you had identified a situaion where you expect to have at least=
 a warning please create a new fire ticket and describe the situation may b=
e with an example project which reproduces the wrong behaviour. ATM i have =
created only warnings no flag...but this does not work correctly....Would b=
e great...Apart from that thanks for you feedback anyway.

> Artifacts with same artifactId/version are ignored in packaging
> ---------------------------------------------------------------
>
>                 Key: MEAR-180
>                 URL: https://jira.codehaus.org/browse/MEAR-180
>             Project: Maven Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.9
>            Reporter: Reto Habl=FCtzel
>            Assignee: Karl-Heinz Marbaise
>             Fix For: 2.10
>
>         Attachments: ear-silent-ignore.zip
>
>
> 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 i=
t 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-arc=
hives.apache.org/mod_mbox/maven-users/201402.mbox/browser
> 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 \[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\]
> {quote}
> Note that this sample shows how dependent libraries are ignored, but I th=
ink 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
(v6.1.6#6162)