[
https://issues.apache.org/jira/browse/MEAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169352#comment-16169352
]
Karl Heinz Marbaise commented on MEAR-249:
------------------------------------------
Hi, first thanks for your feedback.
yes this was right and the wrong result was generated which is based on the
previous wrong implementation.
The thing is if a user decided to define a different mapping (which is now no
problem with the new implementation) which would clash in names (same file
name) there should be an error cause otherwise it would not being fixed and
would produce wrong results in the resulting EAR file...(which means
overwriting of existing files!)..
> Maven EAR plugin - two libraries with a same ArtifactId
> -------------------------------------------------------
>
> Key: MEAR-249
> URL: https://issues.apache.org/jira/browse/MEAR-249
> Project: Maven Ear Plugin
> Issue Type: Bug
> Affects Versions: waiting-for-feedback
> Reporter: Tomas Tulka
>
> When an EAR module has two (or more) dependencies with a same artifactId,
> Maven copy those into the /lib directory and one rewrites the other. In the
> end there is only one library in the EAR.
> This is not what I would expect, because it is correct to have such
> dependencies. The plugin should deal with it or print a warning (it's a
> tricky issue when it is about transitive dependencies).
> <dependency>
> <groupId>com.group1</groupId>
> <artifactId>same-artifact</artifactId>
> </dependency>
> <dependency>
> <groupId>com.group2</groupId>
> <artifactId>same-artifact</artifactId>
> </dependency>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
