[
http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185236#action_185236
]
Brian Fox commented on MNG-4257:
--------------------------------
Expecting to have to copies of the same jar with different versions not clash
is counter-intuitive. Supporting it in Maven is definitely not trivial and it
would probably cause far more troubles than it solves. Think about what could
happen if people accidentally define the same dependency twice. What will be a
parsing error now suddenly becomes an allowable edge case that 99% of the time
breaks someone's product at runtime. +1 to won't 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
