[
https://jira.codehaus.org/browse/MNG-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324098#comment-324098
]
Robert Balazsi commented on MNG-5432:
-------------------------------------
I tested this scenario on 3.0.5 and it works correctly, so I guess it has been
fixed.
> Range [1.3, 1.4) cannot get resolved, but [1.3],[1.4] is working.
> -----------------------------------------------------------------
>
> Key: MNG-5432
> URL: https://jira.codehaus.org/browse/MNG-5432
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0.4
> Environment: Win 7 Pro 64 Bit, JDK 1.7.0_13, Nexus 1.9.2.4, MVN 3.0.4
> Reporter: Markus KARG
> Priority: Critical
>
> My project contains the following dependency:
> <dependency>
> <groupId>xmlunit</groupId>
> <artifactId>xmlunit</artifactId>
> <version>[1.3, 1.4)</version>
> <scope>test</scope>
> </dependency>
> This worked well until today, as on Maven Central the latest artifact was 1.3.
> Today in Maven Central a version 1.4 was published, and now my project does
> not build anymore!
> "mvn compile" says that it cannot find an xmlunit artifact in the range [1.3,
> 1.4). This is strange, as 1.3 is still found in my local repo, in my Nexus
> instance, and on Maven Central!
> I was able to workaround it by using
> <dependency>
> <groupId>xmlunit</groupId>
> <artifactId>xmlunit</artifactId>
> <version>[1.3]</version>
> <scope>test</scope>
> </dependency>
> instead, which is some kind of weird.
> Seems like a bug in the range resolver?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
