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
javadoc suggests bracket version bracket or [version] for exact match
http://maven.apache.org/plugins/maven-enforcer-plugin/rules/versionRanges.html
if you specify a specifiv version such as 1.3and you get any
other version such as 1.1 or 1.2 then that is a bugperhaps a 1.2 or 1.1 was
installe
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
