[
http://jira.codehaus.org/browse/MEV-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120922
]
Carlos Sanchez commented on MEV-570:
------------------------------------
when you add a dependency, don't you have to check that everything still works
with your code? or you just change a version of a library and ship it to
production?
this is a one time thing for old projects that use non qualified groupIds and
they are moving to the new groupId. If the project decides to do so you ask
them why, as if they decide to break the API, remove classes or whatever they
want to do
the most I can do is add a relocation pom for NEW versions so you'll get a
warning if you upgrade using the old groupId, and then you should figure out
why you get that warning
old versions are not relocated because as it's implemented now it can break old
builds, NOT to save me some time
if you want to implement a new method you are more than welcome. Check the
mailing lists and jira MNG as the issue was raised before but nobody
implemented it
> 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
