[jira] Commented: (MNG-4257) Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version
[ http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185214#action_185214 ] Benjamin Bentmann commented on MNG-4257: bq. I'm inclined to close as 'won't fix'. +1, leaving the version out of consideration is quite an essential precondition for model inheritance, profile injection, dependency management and conflict resolution. 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
[jira] Commented: (MNG-4257) Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version
[ http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] Commented: (MNG-4257) Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version
[ http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=185138#action_185138 ] Brett Porter commented on MNG-4257: --- @Joerg that's not uncommon (antlr did the same). I don't think that's a problem for Maven to solve. Surely the JARs can co-exist, but don't need to. If they are actually complimentary, then I think naming them differently (Maven or not) is a good idea. I'm inclined to close as '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
[jira] Commented: (MNG-4257) Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version
[ http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184951#action_184951 ] Joerg Schaible commented on MNG-4257: - @Brian: Actually there is really an issue with this! Please have a look at all the discussion regarding naming schemes on commons-dev on what to do about upcoming commons releases (e.g. like commons-lang-3.0) that will make use of the JDK 5, improve and optimize API itself and drop all the old deprecated stuff. Basically we agreed that we will release a version that can be used side-by-side with a jar from the commons-lang-2.x series (well, we have no real choice here, the library is used in a lot of deps), but the current naming scheme will force us to name the next version with something along to org.apache.commons:commons-lang3:3.x. 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
[jira] Commented: (MNG-4257) Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version
[ http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184808#action_184808 ] Brian Fox commented on MNG-4257: I honestly think this is a bad idea, it's not normal to require the same dependency twice in your classpath and it shouldn't be allowed / encouraged by maven. 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
[jira] Commented: (MNG-4257) Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version
[ http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
