Sean, You trimmed a bit too much of the error message. What is the whole dependency path?
I cannot repro this with maven 2.1.0. I cleaned my repository, so if there was a problem here I should reproduce it. The error is saying that some POM has a <parent/> for the parent project, but cannot find it via the relativePath. But I can't tell which POM from what you posted, and it works fine for me. --benson On Mon, Jul 20, 2009 at 6:57 AM, Sean Owen<sro...@gmail.com> wrote: > FYI If I roll back the last change to the core pom.xml, for > MAHOUT-144, it works. > > On Mon, Jul 20, 2009 at 11:37 AM, Sean Owen<sro...@gmail.com> wrote: >> PS I am still getting this error -- can't mvn clean, install, >> anything. Am I the only one? does this indicate what I might be doing >> wrong? >> >> On Fri, Jul 17, 2009 at 2:05 PM, Sean Owen<sro...@gmail.com> wrote: >>> On a related note, I get this error now when building from head: >>> >>>> mvn install >>> >>> ... >>> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: >>> Unable to download the artifact from any repository >>> >>> org.apache.mahout:mahout-parent:pom:0.2-SNAPSHOT >>> >>> from the specified remote repositories: >>> central (http://repo1.maven.org/maven2), >>> gson (http://google-gson.googlecode.com/svn/mavenrepo), >>> Apache snapshots (http://people.apache.org/maven-snapshot-repository) >>> ... >> >
