You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2008/02/15 23:50:28 UTC

[jira] Updated: (MWAR-132) dependencies with same artifactId and != groupId result is conflicts in WEB-INF/lib

     [ http://jira.codehaus.org/browse/MWAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MWAR-132:
------------------------------

         Assignee: Olivier Lamy
    Fix Version/s: 2.1

> dependencies with same artifactId and != groupId result is conflicts in WEB-INF/lib
> -----------------------------------------------------------------------------------
>
>                 Key: MWAR-132
>                 URL: http://jira.codehaus.org/browse/MWAR-132
>             Project: Maven 2.x War Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.1-alpha-1
>            Reporter: nicolas de loof
>            Assignee: Olivier Lamy
>            Priority: Minor
>             Fix For: 2.1
>
>
> as discussed on dev mailing list (groupId/artifactId mapping for Eclipse jars) the War plugin may fail creating the webapp WEB-INF/lib if multiple dependencies use the same artifactId, but different groupIds.
> This is not the case now as many libs are created with maven1 "Id" in mind, for example all apache commons having "commons-" as artifactId prefix. In future, some libs may start using simplier names and rely more on maven groupId. For such case, the war plugin MAY provide and option to add groupIds to artifacts copied to WEB-INF/lib.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira