[
https://jira.codehaus.org/browse/MEAR-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MEAR-180.
------------------------------------
Resolution: Not A Bug
Assignee: Karl-Heinz Marbaise
I would suggest to use the {{fileNameMapping}} option of ear plugin like the
following:
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<version>2.9</version>
<configuration>
<defaultLibBundleDir>lib</defaultLibBundleDir>
<fileNameMapping>full</fileNameMapping>
</configuration>
</plugin>
</plugins>
</build>
{code}
which will solve your problem. Based on the solution i will close this issue.
If you have any objection don't hesitate to reopen the issue.
> Artifacts with same ID 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ützel
> Assignee: Karl-Heinz Marbaise
> 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 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:
> {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 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
(v6.1.6#6162)
