[
http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184830#action_184830
]
Alexandre Navarro commented on MNG-4257:
----------------------------------------
I agree with you but I have no other choice in my case. To resolve my problem
in my firm, I uploaded the same lib with another groupId. It is not a great
solution but I don't have another solution.
I understand if you don't want to fix.
> Add the possibility to have 2 dependencies with the same groupId:artifactId
> but not the same version
> ----------------------------------------------------------------------------------------------------
>
> Key: MNG-4257
> URL: http://jira.codehaus.org/browse/MNG-4257
> Project: Maven 2
> Issue Type: New Feature
> Reporter: Alexandre Navarro
> Assignee: Brian Fox
>
> Add the possibility to have 2 dependencies with the same groupId:artifactId
> but not the same version.
> For instance, when you have two versions of a jar with a refactoring of a
> package like dozer 4 and 5.
> In my application, I use dozer 5 but I have a dependency which uses dozer 4.
> As maven considers by default all libs are ascendant compatibility, I don't
> have dozer 4 in my classpath and so my depency does not work.
> It can be useful to force not to resolve some conflict.
> I don't think it is possible to do that with maven.
--
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
