You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2018/03/04 18:58:00 UTC

[jira] [Closed] (MEAR-249) Maven EAR plugin - two libraries with a same ArtifactId

     [ https://issues.apache.org/jira/browse/MEAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise closed MEAR-249.
------------------------------------
    Resolution: Incomplete
      Assignee: Karl Heinz Marbaise

This has been fixed by MEAR-171

> 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
>            Assignee: Karl Heinz Marbaise
>            Priority: Major
>
> 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
(v7.6.3#76005)