[ 
https://issues.apache.org/jira/browse/MEAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169345#comment-16169345
 ] 

Tomas Tulka commented on MEAR-249:
----------------------------------

This solution is okay for me, I was just wandering if it wouldn't be possible 
to generate the full name mapping automatically in this case, or to create an 
indexing for the same artifact files, something like `same-artifact.jar` and 
`same-artifact (1).jar` in the example above.

The point here is, there is nothing wrong with the artifacts, everything is 
valid and a wrong result is generated. It means ERROR is inappropriate here.

But the WARNING with the hint is probably sufficient enough.

Thank you!

> 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)

Reply via email to