On Thu, May 22, 2008 at 10:41 PM, kawazu <[EMAIL PROTECTED]> wrote: > Folks; > > after merrily using maven2 for quite a while, by now I dealt with > defining dependency using version ranges for the first time - and > failed, not sure why. Maybe I am just too stupid, and maybe someone can > help me outta this? > > Example: Dependency defined is > > <dependency> > <groupId>jmimemagic</groupId> > <artifactId>jmimemagic</artifactId> > <version>[0.1,)</version> > <scope>compile</scope> > </dependency> > > > Looking to repo1.maven.org/maven2/jmimemagic/jmimemagic, I see there are > three different artifacts around (0.0.4a, 0.1.1, 0.1.2), and so as I > understodd this kind of version specification, I'd kinda expect maven to > use 0.1.2 in this situation. However, running "mvn -U install" on the > project ends up like this: > > [...] > Couldn't find a version in [0.0.4a] to match range [0.1,) > jmimemagic:jmimemagic:jar:null > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > [...] > > > Not quite what I expected to happen. My fault, or something I just > misunderstood? Maven version is 2.0.8, running a pretty recent Sun JDK... :/ > > TIA and best regards, > Kristian
The problem in this case is the broken metadata: http://repo1.maven.org/maven2/jmimemagic/jmimemagic/maven-metadata.xml it lists only version 0.0.4a - Henry --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
