Whoops,

Below is a copy of mavens output.

INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.mahout:mahout:pom:0.4-SNAPSHOT

Reason: Cannot find parent: org.apache:apache for project: 
org.apache.mahout:mahout:pom:0.4-SNAPSHOT for project 
org.apache.mahout:mahout:pom:0.4-SNAPSHOT


[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent: 
org.apache:apache for project: org.apache.mahout:mahout:pom:0.4-SNAPSHOT for 
project org.apache.mahout:mahout:pom:0.4-SNAPSHOT
  at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
  at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)
  at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
  at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
  at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
  at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find 
parent: org.apache:apache for project: 
org.apache.mahout:mahout:pom:0.4-SNAPSHOT for project 
org.apache.mahout:mahout:pom:0.4-SNAPSHOT
  at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
  at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
  at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
  at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
  at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
  at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
  at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
  ... 12 more
Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 
POM. for project org.apache:apache at 
/home/stevens35/.m2/repository/org/apache/apache/6/apache-6.pom
  at 
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1599)
  at 
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1571)
  at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:562)
  at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
  ... 18 more
[INFO] ------------------------------------------------------------------------
"build.err" 48L, 3437C

________________________________________
From: Grant Ingersoll [[email protected]]
Sent: Tuesday, August 24, 2010 10:36 AM
To: [email protected]
Subject: Re: Compiling Mahout with maven

On Aug 24, 2010, at 1:19 PM, Stevens, Keith D. wrote:

> Hi All,
>
> I'm trying to use mahout on a small cluster that has hadoop installed, but 
> i've run into problems with building.  I checked out a copy of the trunk via 
> svn and tried to run "mvn install" in the top level mahout directory.  On my 
> local machine, this works fine and generates the expected jars and job files. 
>  On the small cluster, everything goes wrong.  From what i've found so far, 
> the problem is very similar to what is mentioned in 
> http://*www.*lucidimagination.com/search/document/971d3227003175a8/mvn_install_error#971d3227003175a8,
>  except that none of the suggested solutions seem to work.
>
> Attached is a copy of mavens output.

FYI: the mailing list strips attachments.

> I'm currently running maven 2.2.1.  As suggested in the previous issue, I've 
> already deleted the svn repository and checked it out again, I've also tried 
> deleting the ~/.m2 directory.  Neither solution worked.
>
> Any suggestions would be greatly appreciated.
>
> Thanks!
> --Keith Stevens

--------------------------
Grant Ingersoll
http://*lucenerevolution.org Lucene/Solr Conference, Boston Oct 7-8


Reply via email to