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 <[email protected]> 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: [email protected] For additional commands, e-mail: [email protected]
