[
http://jira.codehaus.org/browse/MEV-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120859
]
Carlos Sanchez commented on MEV-570:
------------------------------------
it's not that trivial, if you put relocation poms for old releases you can
break builds, that's why old things don't get changed (we had this discussion
before for commons and they decided not to do it). If struts adds the
appropriate exclusion then it's going to be transparent for all struts users.
For reference see MAVENUPLOAD-1419
> groupId org.freemarker and freemarker refer to the same product
> ---------------------------------------------------------------
>
> Key: MEV-570
> URL: http://jira.codehaus.org/browse/MEV-570
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Relocation
> Reporter: Al Sutton
> Assignee: Carlos Sanchez
>
> Both org.freemarker and freemarker refer to the same product (the freemarker
> template library), 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 2.3.4 from groupID freemarker from
> a dependancy, and 2.3.11 from org.freemarker in our pom.
> One needs to go and a redirect put in place inorder to ensure consistency.
--
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
