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 <[email protected]> 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 <[email protected]>
> 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" <[email protected]> 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
