You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mahout.apache.org by Max Heimel <mh...@googlemail.com> on 2009/10/18 17:13:41 UTC

Building Mahout

Hi all,

I am running into some problems when trying to build a mahout from the
current SVN repository.
I followed the instructions from:
http://cwiki.apache.org/MAHOUT/buildingmahout.html
However, the first command "mvn install" in mahout/trunk aborts after
downloading some stuff and (successfully) running tests with the
following error:

[INFO] [gpg:sign {execution: sign-artifacts}]
GPG Passphrase: *
Reading passphrase from file descriptor 0
gpg: no default secret key
gpg: signing failed
[INFO] ---------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ---------------------------------------------------------------------
[INFO] Exit code: 2

When I rerun maven install with the -e switch I get the following error:

[INFO] ---------------------------------------------------------------------
[INFO] Building Mahout coure
[INFO]      task-segment: [install]
[INFO] ---------------------------------------------------------------------
[INFO] ---------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ---------------------------------------------------------------------
[INFO] 'copy-resources' was specified in an execution, but not found
in the plugin
[INFO] ---------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecylce.LifecycleExecutionException:
'copy-resources' was specified in an execution, but not found in the
plugin
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindExecutionToLifecycle(DefaultLifecycleExecutor.java:1359)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1260)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1004)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
            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(Lauhcer.java:375)

I am a bit at loss here... When I remove the ~/.m2 folder, the second
error disappears - however, I have to recompile and retest everything
and then run into the first error again. I also tried running maven
with -Dmaven.jar.sign.skip=true, but this didn't help either :(

The Mahout source is checked out from svn at revison 826431, I use
maven version 2.0.10 (I also tried 2.2.1 with the same result) and the
sun JDK 1.6.0_16.

Thanks,
Max

Re: Building Mahout

Posted by Sean Owen <sr...@gmail.com>.
Funny you should ask as I just attempted to build the RC an hour ago.
I got hung up on some gpg:sign plugin issue. Hoping mahout-dev can
help me out (or anyone familiar with Maven and GPG) since that's all
that stands in the way. What's in SVN now is what 0.2 will be.

I at least agree that releases should come more quickly, and will push
to have 0.3 out in more like 2 months rather than 6.

On Tue, Oct 20, 2009 at 5:00 PM, Patrick Angeles
<pa...@gmail.com> wrote:
> Any idea when the 0.2 RC will be available via the central maven repo? Also,
> it might be useful to support snapshot builds so people can integrate with
> the latest version using maven. I can pitch in if there's general agreement
> on the value of this...

Re: Building Mahout

Posted by Patrick Angeles <pa...@gmail.com>.
Any idea when the 0.2 RC will be available via the central maven repo? Also,
it might be useful to support snapshot builds so people can integrate with
the latest version using maven. I can pitch in if there's general agreement
on the value of this...

On Mon, Oct 19, 2009 at 4:47 PM, Sean Owen <sr...@gmail.com> wrote:

> I suspect this is actually related to a change that I think Isabel
> committed today? Lots of stuff going in now for an 0.2 release
> candidate. It should be unrelated to the last issue.
>
> On Mon, Oct 19, 2009 at 9:42 PM, Chris Suter <cg...@gmail.com> wrote:
> > I was also having this problem. Noting its resolution here, I updated my
> > source tree and am now getting a new error -- missing
> > "supplemental-models.xml"
>

Re: Building Mahout

Posted by Chris Suter <cg...@gmail.com>.
yeah sorry to tack it onto an unrelated thread...keep up the good work
folks! really impressive framework!

On Mon, Oct 19, 2009 at 4:47 PM, Sean Owen <sr...@gmail.com> wrote:

> I suspect this is actually related to a change that I think Isabel
> committed today? Lots of stuff going in now for an 0.2 release
> candidate. It should be unrelated to the last issue.
>
> On Mon, Oct 19, 2009 at 9:42 PM, Chris Suter <cg...@gmail.com> wrote:
> > I was also having this problem. Noting its resolution here, I updated my
> > source tree and am now getting a new error -- missing
> > "supplemental-models.xml"
>



-- 
Christopher Suter
www.grooveshark.com

Re: Building Mahout

Posted by Sean Owen <sr...@gmail.com>.
I suspect this is actually related to a change that I think Isabel
committed today? Lots of stuff going in now for an 0.2 release
candidate. It should be unrelated to the last issue.

On Mon, Oct 19, 2009 at 9:42 PM, Chris Suter <cg...@gmail.com> wrote:
> I was also having this problem. Noting its resolution here, I updated my
> source tree and am now getting a new error -- missing
> "supplemental-models.xml"

Re: Building Mahout

Posted by Chris Suter <cg...@gmail.com>.
I was also having this problem. Noting its resolution here, I updated my
source tree and am now getting a new error -- missing
"supplemental-models.xml"

$ mvn compile
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Apache Lucene Mahout
[INFO]   Mahout Common Maven Parent
[INFO]   Mahout core
[INFO]   Mahout Taste Webapp
[INFO]   Mahout utilities
[INFO]   Mahout examples
[INFO]
------------------------------------------------------------------------
[INFO] Building Apache Lucene Mahout
[INFO]    task-segment: [compile]
[INFO]
------------------------------------------------------------------------
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[ERROR] Error loading supplemental data models: Could not find resource
'supplemental-models.xml'.
org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not
find resource 'supplemental-models.xml'.
        at
org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsInputStream(DefaultResourceManager.java:91)
        at
org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:117)
        at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.loadSupplements(ProcessRemoteResourcesMojo.java:928)
        at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:410)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        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)
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error loading supplemental data models: Could not find resource
'supplemental-models.xml'.

[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Mon Oct 19 16:40:18 EDT 2009
[INFO] Final Memory: 11M/102M
[INFO]
------------------------------------------------------------------------


Just to be sure, I deleted my local copy and checked out a fresh copy from
svn. Haven't tried wiping my ~/.m2/repo but that seems unlikely to be the
problem, and isn't my favorite solution to anything.

On Sun, Oct 18, 2009 at 5:59 PM, Sean Owen <sr...@gmail.com> wrote:

> I changed the phase it applies to to 'deploy' which is probably more
> appropriate. Still need to see where it generates the sigs, make sure
> it does deploy sigs properly. But 'install' should not trigger signing
> now.
>
> On Sun, Oct 18, 2009 at 5:05 PM, Grant Ingersoll <gs...@apache.org>
> wrote:
> >
> > On Oct 18, 2009, at 11:45 AM, Sean Owen wrote:
> >
> >> That is right, or rather, adjust the phase that the plugin applies to. I
> >> think it is 'verify' now and I imagine there is something that us more
> >> like
> >> release.
> >
> > There is a release profile in the POM, I think you can hook in the
> signing
> > into that part.  I'll try to take a look later this afternoon.
> >
> >>
> >> This is where I still don't understand how maven is supposed to work. I
> >> still find maven a big ol pain. Would appreciate the maven fans stepping
> >> in
> >> to look at this.
> >>
> >> Should people be running install anyway? Vs compile?
> >>
> >> On Oct 18, 2009 4:36 PM, "Grant Ingersoll" <gs...@apache.org> wrote:
> >>
> >> Hmm, Sean was just trying some things out here for the release.  We
> >> probably
> >> need to revert the change.  The signing only needs to take place during
> a
> >> release.
> >>
> >> -Grant
> >>
> >> On Oct 18, 2009, at 11:13 AM, Max Heimel wrote: > Hi all, > > I am
> running
> >> into some problems whe...
> >
> >
>



-- 
Christopher Suter
www.grooveshark.com

Re: Building Mahout

Posted by Sean Owen <sr...@gmail.com>.
I changed the phase it applies to to 'deploy' which is probably more
appropriate. Still need to see where it generates the sigs, make sure
it does deploy sigs properly. But 'install' should not trigger signing
now.

On Sun, Oct 18, 2009 at 5:05 PM, Grant Ingersoll <gs...@apache.org> wrote:
>
> On Oct 18, 2009, at 11:45 AM, Sean Owen wrote:
>
>> That is right, or rather, adjust the phase that the plugin applies to. I
>> think it is 'verify' now and I imagine there is something that us more
>> like
>> release.
>
> There is a release profile in the POM, I think you can hook in the signing
> into that part.  I'll try to take a look later this afternoon.
>
>>
>> This is where I still don't understand how maven is supposed to work. I
>> still find maven a big ol pain. Would appreciate the maven fans stepping
>> in
>> to look at this.
>>
>> Should people be running install anyway? Vs compile?
>>
>> On Oct 18, 2009 4:36 PM, "Grant Ingersoll" <gs...@apache.org> wrote:
>>
>> Hmm, Sean was just trying some things out here for the release.  We
>> probably
>> need to revert the change.  The signing only needs to take place during a
>> release.
>>
>> -Grant
>>
>> On Oct 18, 2009, at 11:13 AM, Max Heimel wrote: > Hi all, > > I am running
>> into some problems whe...
>
>

Re: Building Mahout

Posted by Grant Ingersoll <gs...@apache.org>.
On Oct 18, 2009, at 11:45 AM, Sean Owen wrote:

> That is right, or rather, adjust the phase that the plugin applies  
> to. I
> think it is 'verify' now and I imagine there is something that us  
> more like
> release.

There is a release profile in the POM, I think you can hook in the  
signing into that part.  I'll try to take a look later this afternoon.

>
> This is where I still don't understand how maven is supposed to  
> work. I
> still find maven a big ol pain. Would appreciate the maven fans  
> stepping in
> to look at this.
>
> Should people be running install anyway? Vs compile?
>
> On Oct 18, 2009 4:36 PM, "Grant Ingersoll" <gs...@apache.org>  
> wrote:
>
> Hmm, Sean was just trying some things out here for the release.  We  
> probably
> need to revert the change.  The signing only needs to take place  
> during a
> release.
>
> -Grant
>
> On Oct 18, 2009, at 11:13 AM, Max Heimel wrote: > Hi all, > > I am  
> running
> into some problems whe...


Re: Building Mahout

Posted by Sean Owen <sr...@gmail.com>.
That is right, or rather, adjust the phase that the plugin applies to. I
think it is 'verify' now and I imagine there is something that us more like
release.

This is where I still don't understand how maven is supposed to work. I
still find maven a big ol pain. Would appreciate the maven fans stepping in
to look at this.

Should people be running install anyway? Vs compile?

On Oct 18, 2009 4:36 PM, "Grant Ingersoll" <gs...@apache.org> wrote:

Hmm, Sean was just trying some things out here for the release.  We probably
need to revert the change.  The signing only needs to take place during a
release.

-Grant

On Oct 18, 2009, at 11:13 AM, Max Heimel wrote: > Hi all, > > I am running
into some problems whe...
--------------------------
Grant Ingersoll
http://www.lucidimagination.com/

Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using
Solr/Lucene:
http://www.lucidimagination.com/search

Re: Building Mahout

Posted by Grant Ingersoll <gs...@apache.org>.
Hmm, Sean was just trying some things out here for the release.  We  
probably need to revert the change.  The signing only needs to take  
place during a release.

-Grant

On Oct 18, 2009, at 11:13 AM, Max Heimel wrote:

> Hi all,
>
> I am running into some problems when trying to build a mahout from the
> current SVN repository.
> I followed the instructions from:
> http://cwiki.apache.org/MAHOUT/buildingmahout.html
> However, the first command "mvn install" in mahout/trunk aborts after
> downloading some stuff and (successfully) running tests with the
> following error:
>
> [INFO] [gpg:sign {execution: sign-artifacts}]
> GPG Passphrase: *
> Reading passphrase from file descriptor 0
> gpg: no default secret key
> gpg: signing failed
> [INFO]  
> ---------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]  
> ---------------------------------------------------------------------
> [INFO] Exit code: 2
>
> When I rerun maven install with the -e switch I get the following  
> error:
>
> [INFO]  
> ---------------------------------------------------------------------
> [INFO] Building Mahout coure
> [INFO]      task-segment: [install]
> [INFO]  
> ---------------------------------------------------------------------
> [INFO]  
> ---------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]  
> ---------------------------------------------------------------------
> [INFO] 'copy-resources' was specified in an execution, but not found
> in the plugin
> [INFO]  
> ---------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecylce.LifecycleExecutionException:
> 'copy-resources' was specified in an execution, but not found in the
> plugin
>            at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindExecutionToLifecycle 
> (DefaultLifecycleExecutor.java:1359)
>            at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle 
> (DefaultLifecycleExecutor.java:1260)
>            at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings 
> (DefaultLifecycleExecutor.java:1004)
>            at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal 
> (DefaultLifecycleExecutor.java:477)
>            at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures 
> (DefaultLifecycleExecutor.java:330)
>            at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments 
> (DefaultLifecycleExecutor.java:291)
>            at  
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute 
> (DefaultLifecycleExecutor.java:142)
>            at org.apache.maven.DefaultMaven.doExecute 
> (DefaultMaven.java:336)
>            at org.apache.maven.DefaultMaven.execute 
> (DefaultMaven.java:129)
>            at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>            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(Lauhcer.java:375)
>
> I am a bit at loss here... When I remove the ~/.m2 folder, the second
> error disappears - however, I have to recompile and retest everything
> and then run into the first error again. I also tried running maven
> with -Dmaven.jar.sign.skip=true, but this didn't help either :(
>
> The Mahout source is checked out from svn at revison 826431, I use
> maven version 2.0.10 (I also tried 2.2.1 with the same result) and the
> sun JDK 1.6.0_16.
>
> Thanks,
> Max

--------------------------
Grant Ingersoll
http://www.lucidimagination.com/

Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids)  
using Solr/Lucene:
http://www.lucidimagination.com/search