[
https://jira.codehaus.org/browse/MNG-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4530:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Add alias feature for moved/renamed dependencies
> ------------------------------------------------
>
> Key: MNG-4530
> URL: https://jira.codehaus.org/browse/MNG-4530
> Project: Maven
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
