[jira] Commented: (MNG-4530) Add alias feature for moved/renamed dependencies

["Pete Muir (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208109#action_208109 ] 

Pete Muir commented on MNG-4530:
--------------------------------

Project Jigsaw calls this "provides"

"The clause provides P indicates that a dependency on module P by some other module may be satisfied by module M."

> Add alias feature for moved/renamed dependencies
> ------------------------------------------------
>
>                 Key: MNG-4530
>                 URL: http://jira.codehaus.org/browse/MNG-4530
>             Project: Maven 2 & 3
>          Issue Type: New Feature
>          Components: Dependencies
>            Reporter: Paul Gier
>
> There should be an option to link multiple dependency groupId/artifactIds so that the dependency resolver knows they refer to the same artifact.  There are many dependencies that get renamed to a new groupId/artifactId.  This causes problems because many times the old groupId/artifactId is still pulled in transitively from other projects.  Currently, the only way to do this is with a tedious combination of <excludes> tags and enforcer rules.  It would be much simpler if there were a mechanism in the pom and dependency manager to treat two IDs as the same dependency.
> {code:xml}
> <dependency>
>   <groupId>org.mycomp</groupId>
>   <artifactId>log4j</groupId>
>   <version>1.0</version>
>   <aliases>
>     <alias>
>       <groupId>log4j</groupId>
>       <artifactId>log4j</artifactId>
>     <alias>
>   </aliases>
> <dependency>
> {code}

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