[
http://jira.codehaus.org/browse/MEV-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MEV-571.
------------------------------
Assignee: Carlos Sanchez
Resolution: Won't Fix
you need to use exclusions in your pom if you see that behavior
the repository is provided by the project and if they decide to move to a new
groupId is something between you and them and thier upgrade instructions for
new versions
> velocity and org.apache.velocity refer to the same product
> ----------------------------------------------------------
>
> Key: MEV-571
> URL: http://jira.codehaus.org/browse/MEV-571
> Project: Maven Evangelism
> Issue Type: Bug
> Reporter: Al Sutton
> Assignee: Carlos Sanchez
>
> Both groupIds org.apache.velocity and velocity refer to the same product (the
> velocity template engine), having two different groupIDs for the same product
> creates the possibility for multiple jars of the same product to be included
> in a compile and run classpath.
> This has been seen in Struts2 where we had 1.4 from groupID velocity from a
> dependancy, and 1.5 from org.apache.velocity in our pom.
> One needs to go and a redirect put in place inorder to ensure correct
> dependancy resolution.
--
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
