uot;.
>
> > -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!
> >
>
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&
?
> -Original Message-
> From: Martin Gainty [mailto:mgai...@hotmail.com]
> Sent: Mittwoch, 25. Juli 2012 16:14
> To: users@maven.apache.org
> Subject: RE: "No versions available" but actually local repository
> contains it!
> Importance: High
>
>
> javadoc sugg
pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Subject: "No versions available" but actually local repository contains it!
> D
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 at
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 succ
