Hey Markus, I happened to be working in a project that currently uses hamcrest-core 1.1 transitively via junit 4.10, we also use nexus. If I add an explicit dependency for org.hamcrest:hamcrest-core:[1.3] to the pom I get the requested 1.3 version as expected. I tested this on 2 machines: my Mac desktop with maven 3.0.3; and my old linux desktop with maven 3.0.4. Both systems behave as expected (i.e. maven resolves the artifact to version 1.3). Both systems began without the artifact in their local repository.
Since you said in your original post that you tried specifying versions [1.2] and 1.2 and maven resolved these to 1.2 and 1.1 respectively, there must be some other dependency of your project that either explicitly or transitively is depending on version 1.1 (my bet is on junit ;). To help you diagnose the problem further, try running mvn -X dependency:tree | grep hamcrest. This will show you how maven is resolving the version of the hamcrest artifacts. You may also want to double-check the checksums of the 1.3 artifact against central. I recall a recent thread where a corrupted artifact made it appear to maven that the artifact didn't exist and the error message was hiding the underlying corruption problem. Let us know if the output of that command provides any clues. Cheers, Doug On Thu, Jul 26, 2012 at 11:51 AM, Markus KARG <mar...@headcrashing.eu>wrote: > How does that explain the local behaviour? I remove everything (the > complete groupId folder) from my local repo and Nexus instance, trigger a > build, and get the same problem again: The file with version 1.3 is then > found in Nexus and local repo, but maven still says that 1.3 is not > existing when forcing [1.3]. BTW, the problematic artifact is > "org.hamcrest:hamcrest-core:1.3". > > > -----Original Message----- > > From: Milos Kleint [mailto:mkle...@gmail.com] > > Sent: Mittwoch, 25. Juli 2012 09:33 > > To: Maven Users List > > Subject: Re: "No versions available" but actually local repository > > contains it! > > > > there's some code in latest maven that not only checks the presence of > > the jar/pom in local repository but also some additional metadata which > > describes where it was downloaded from. where is defined by repository > > id. if the repository id in your project is missing in the current > > metadata, a new attempt will be made to download it. if it fails, the > > build fails as well. That way maven shoudl enforce that your project is > > always buildable with given pom content. > > > > Milos > > > > On Wed, Jul 25, 2012 at 9:27 AM, Markus Karg <k...@quipsy.de> wrote: > > > I have a very strange problem with Maven 3.0.4 running on JDK > > 1.6.0_26 > > > on Win 7 Pro SP1 (64 Bit): > > > > > > > > > > > > When I want to compile, Maven says that it cannot resolve a > > dependency: > > > "No versions available for org.hamcrest:hamcrest-core:jar:[1.3,1.3] > > > within specified range". But actually, Maven in fact successfully > > > downloaded exactly that JAR and POM in exactly that version from > > Nexus > > > (hence, from Maven Central in turn), as I can see the JAR and POM in > > > both, my local repository and my Nexus instance! The weird thing is, > > > if I replace [1.3] by [1.2] it does NOT complain about missing > > dependency! > > > Weird, isn't it? > > > > > > > > > > > > And it gets even more weird: If I change my POM to relax the > > requested > > > range from [1.2] to simply "1.2" (without braces, just to see what > > > happens) it downloads version 1.1. But for what, if a 1.2 and 1.3 > > > already are there? > > > > > > > > > > > > How can I fix this? I definitively need version 1.3, which IS > > > available in my local repository, my Nexus instance and Maven > > Central! > > > > > > > > > > > > Thanks a lot! > > > > > > Markus > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
