[ http://jira.codehaus.org/browse/MNG-2331?page=all ]
Carlos Sanchez closed MNG-2331:
-------------------------------
Assign To: Carlos Sanchez
Resolution: Won't Fix
Relocation is per version. You may experience that problem during the
transition from one group name to another
> redirected artifacts do not evict against/collide with non-redirected
> artifacts
> -------------------------------------------------------------------------------
>
> Key: MNG-2331
> URL: http://jira.codehaus.org/browse/MNG-2331
> Project: Maven 2
> Type: Bug
> Components: Dependencies
> Versions: 2.0.4
> Reporter: Andreas Schildbach
> Assignee: Carlos Sanchez
>
>
> For example, add the following dependencies to your project:
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.1.1</version>
> </dependency>
> <dependency>
> <groupId>ehcache</groupId>
> <artifactId>ehcache</artifactId>
> <version>1.2</version>
> </dependency>
> The second dependency is in fact a redirect to the net.sf.ehcache groupId.
> You'll end up with both ehcache 1.1 (as a dependency of hibernate) and
> ehcache 1.2 in your classpath. This also happens if you directly use the
> redirected groupId instead:
> <dependency>
> <groupId>net.sf.ehcache</groupId>
> <artifactId>ehcache</artifactId>
> <version>1.2</version>
> </dependency>
> I can understand that Maven cannot know which artifacts are pointing towards
> a specific artifact in the second case, but at least the first case could be
> handled correctly.
--
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
