[
http://jira.codehaus.org/browse/MEV-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120947
]
Al Sutton commented on MEV-570:
-------------------------------
We have unit tests to check compatibility with new library versions, but with
the duplicate groupId problem we can update all of the dependencies in our
project to the latest version, but because of this problem if a dependency
further down the chain is using a different groupId for the same product the
tests will not be valid because the old version of the library is still being
included on the classpath (as happened with freemarker), and the only way of
finding out is looking at the maven output and checking for duplicates on the
classpath.
I guess you can only do what you feel is best. For us, maybe the way to go is
look for a repository with tighter controls which avoids the duplicate groupID
problem.
> 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
