Ok, some good news. I just did the same test with Maven 3.0.1 and it worked no problem. It downloaded the new version from the remote repo like it was supposed to.
But I don't know if I'm ready to migrate to Maven 3.x yet... Phillip On Thu, Dec 9, 2010 at 10:00 PM, Phillip Hellewell <ssh...@gmail.com> wrote: > I'm using Maven 2.2.1. It won't resolve a dependency with a locked > down version like [1.0.0.6] if the metadata xml file in the local repo > does not have that version. It won't look in my remote repo, which > does have the version I need. But if I delete the metadata xml > file(s) in my local repo, then it works. > > I searched the mail archives and found a lot of topics similar to > this, but I couldn't find a clear enough explanation to understand > whether I'm doing something wrong or if this is just a bug. > > Phillip > > P.S. Here's an example output of the error. > > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > Couldn't find a version in [1.0.0.4, 1.0.0.5] to match range [1.0.0.6,1.0.0.6] > ad.core:cppunitlite:zip:null > > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > adrepo-public (http://maven.example.com:8080/nexus/content/groups/public) > > Path to dependency: > 1) ad.core:core:pom:1.0.0.46-SNAPSHOT > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
