hpi:run and executing a maven job

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

hpi:run and executing a maven job

Erik Ramfelt
Im trying to verify a bug fix for maven jobs in my ci-game plugin. I
start it by running "mvn hpi:run -Djetty.port=8100", and create a
Maven job that checks out the ci-game source tree. But when I build
the job I get a strange error that I can not figure out if its because
a bad setup on my machine or not. Could anyone help me out?


The ci-game POM looks like this:
http://fisheye4.atlassian.com/browse/~raw,r=16903/hudson/trunk/hudson/plugins/ci-game/pom.xml

The error is:
-----------------------------------------------------
At revision 17177
no change for https://svn.dev.java.net/svn/hudson/trunk/hudson/plugins/ci-game
since the previous build
Parsing POMs
ERROR: Failed to parse POMs
org.apache.maven.embedder.MavenEmbedderException: Cannot lookup
required component.
        at hudson.maven.MavenEmbedder.start(MavenEmbedder.java:722)
        at hudson.maven.MavenUtil.createEmbedder(MavenUtil.java:107)
        at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:727)
        at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:675)
        at hudson.FilePath.act(FilePath.java:552)
        at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:425)
        at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:315)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:272)
        at hudson.model.Run.run(Run.java:923)
        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:234)
        at hudson.model.ResourceController.execute(ResourceController.java:93)
        at hudson.model.Executor.run(Executor.java:119)
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Unable to lookup component
'org.apache.maven.project.MavenProjectBuilder', it could not be
started
        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339)
        at org.codehaus.plexus.embed.Embedder.lookup(Embedder.java:78)
        at hudson.maven.MavenEmbedder.start(MavenEmbedder.java:686)
        ... 11 more
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException:
Error starting component
        at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109)
        at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
        at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
        ... 13 more
Caused by: org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException:
Error composing component
        at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:33)
        at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
        at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
        ... 16 more
Caused by: org.codehaus.plexus.component.composition.CompositionException:
Composition failed of field modelInterpolator in object of type
org.apache.maven.project.DefaultMavenProjectBuilder because the
requirement ComponentRequirement{role='org.apache.maven.project.interpolation.ModelInterpolator',
roleHint='null', fieldName='null'} was missing
        at org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:154)
        at org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
        at org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
        at org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
        at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
        ... 18 more
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Unable to lookup component
'org.apache.maven.project.interpolation.ModelInterpolator', it could
not be created
        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
        at org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
        ... 22 more
Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException:
Could not instanciate component: role:
'org.apache.maven.project.interpolation.ModelInterpolator',
implementation:
'org.apache.maven.project.interpolation.RegexBasedModelInterpolator'
        at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77)
        at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62)
        at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
        at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
        at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
        ... 23 more
Caused by: java.lang.NoSuchMethodError:
org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
        at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
        ... 27 more
Finished: FAILURE

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: hpi:run and executing a maven job

blalor
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> On Behalf Of Erik Ramfelt
> Sent: Wednesday, April 15, 2009 8:42 AM
> To: [hidden email]
> Subject: hpi:run and executing a maven job

> Parsing POMs
> ERROR: Failed to parse POMs
> org.apache.maven.embedder.MavenEmbedderException: Cannot lookup
> required component.


I'm getting this same thing with maven-plugin from the 1.299 tag when
attempting to use hpi:run.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: hpi:run and executing a maven job

Kohsuke Kawaguchi
Administrator
In reply to this post by Erik Ramfelt
It looks like Maven inside Hudson and Maven outside Hudson (the one
that you used to launch hpi:run) is interfering.
Which version of Maven do you use to run hpi:run?

2009/4/15 Erik Ramfelt <[hidden email]>:

> Im trying to verify a bug fix for maven jobs in my ci-game plugin. I
> start it by running "mvn hpi:run -Djetty.port=8100", and create a
> Maven job that checks out the ci-game source tree. But when I build
> the job I get a strange error that I can not figure out if its because
> a bad setup on my machine or not. Could anyone help me out?
>
>
> The ci-game POM looks like this:
> http://fisheye4.atlassian.com/browse/~raw,r=16903/hudson/trunk/hudson/plugins/ci-game/pom.xml
>
> The error is:
> -----------------------------------------------------
> At revision 17177
> no change for https://svn.dev.java.net/svn/hudson/trunk/hudson/plugins/ci-game
> since the previous build
> Parsing POMs
> ERROR: Failed to parse POMs
> org.apache.maven.embedder.MavenEmbedderException: Cannot lookup
> required component.
>        at hudson.maven.MavenEmbedder.start(MavenEmbedder.java:722)
>        at hudson.maven.MavenUtil.createEmbedder(MavenUtil.java:107)
>        at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:727)
>        at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:675)
>        at hudson.FilePath.act(FilePath.java:552)
>        at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:425)
>        at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:315)
>        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:272)
>        at hudson.model.Run.run(Run.java:923)
>        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:234)
>        at hudson.model.ResourceController.execute(ResourceController.java:93)
>        at hudson.model.Executor.run(Executor.java:119)
> Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Unable to lookup component
> 'org.apache.maven.project.MavenProjectBuilder', it could not be
> started
>        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339)
>        at org.codehaus.plexus.embed.Embedder.lookup(Embedder.java:78)
>        at hudson.maven.MavenEmbedder.start(MavenEmbedder.java:686)
>        ... 11 more
> Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException:
> Error starting component
>        at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109)
>        at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
>        at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
>        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
>        ... 13 more
> Caused by: org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException:
> Error composing component
>        at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:33)
>        at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
>        at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
>        ... 16 more
> Caused by: org.codehaus.plexus.component.composition.CompositionException:
> Composition failed of field modelInterpolator in object of type
> org.apache.maven.project.DefaultMavenProjectBuilder because the
> requirement ComponentRequirement{role='org.apache.maven.project.interpolation.ModelInterpolator',
> roleHint='null', fieldName='null'} was missing
>        at org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:154)
>        at org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
>        at org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
>        at org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
>        at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
>        ... 18 more
> Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Unable to lookup component
> 'org.apache.maven.project.interpolation.ModelInterpolator', it could
> not be created
>        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
>        at org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
>        ... 22 more
> Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException:
> Could not instanciate component: role:
> 'org.apache.maven.project.interpolation.ModelInterpolator',
> implementation:
> 'org.apache.maven.project.interpolation.RegexBasedModelInterpolator'
>        at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77)
>        at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62)
>        at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
>        at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
>        at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
>        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
>        ... 23 more
> Caused by: java.lang.NoSuchMethodError:
> org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
>        at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63)
>        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>        at java.lang.Class.newInstance0(Class.java:355)
>        at java.lang.Class.newInstance(Class.java:308)
>        at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
>        ... 27 more
> Finished: FAILURE
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>



--
Kohsuke Kawaguchi

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Re: hpi:run and executing a maven job

blalor
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Kohsuke Kawaguchi
> Sent: Wednesday, April 15, 2009 11:02 AM
> To: [hidden email]
> Subject: Re: hpi:run and executing a maven job

> It looks like Maven inside Hudson and Maven outside Hudson (the one
> that you used to launch hpi:run) is interfering.
> Which version of Maven do you use to run hpi:run?

I'm using Maven 2.0.9.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Re: hpi:run and executing a maven job

Kohsuke Kawaguchi
Administrator
Brian, I thought your problem is ClassNotFoundException. Are you
saying you get this exception when you work on a different plugin?

2009/4/15 Lalor, Brian <[hidden email]>:

>> -----Original Message-----
>> From: [hidden email]
>> [mailto:[hidden email]] On Behalf Of Kohsuke Kawaguchi
>> Sent: Wednesday, April 15, 2009 11:02 AM
>> To: [hidden email]
>> Subject: Re: hpi:run and executing a maven job
>
>> It looks like Maven inside Hudson and Maven outside Hudson (the one
>> that you used to launch hpi:run) is interfering.
>> Which version of Maven do you use to run hpi:run?
>
> I'm using Maven 2.0.9.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>



--
Kohsuke Kawaguchi

Bra

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Re: Re: hpi:run and executing a maven job

blalor
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Kohsuke Kawaguchi
> Sent: Wednesday, April 15, 2009 11:17 AM
> To: [hidden email]
> Subject: Re: Re: hpi:run and executing a maven job

> Brian, I thought your problem is ClassNotFoundException. Are you
> saying you get this exception when you work on a different plugin?

I'm getting this with maven-plugin from the hudson-1_299 tag, not the
trunk.  With the trunk, I get the ClassNotFoundException.  I switched to
try to work from code that should be in a known-good state.

The hpi:run problem was resolved by changing to maven 2.0.4 for the
invocation of hpi:run, but I had to add an explicit dependency on
2.0-beta-7 of the release plugin.  2.0-beta-8 requires 2.0.9 (or 2.0.6,
I forget which, now).

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: Re: Re: hpi:run and executing a maven job

Thomas Spengler
The problem is the JDK you are using.
I got this error every time, using the JDK6.
With Jdk5 works.

Tom

> -----Original Message-----
> From: Lalor, Brian [mailto:[hidden email]]
> Sent: Wednesday, April 15, 2009 5:26 PM
> To: [hidden email]
> Subject: RE: Re: Re: hpi:run and executing a maven job
>
> > -----Original Message-----
> > From: [hidden email]
> > [mailto:[hidden email]] On Behalf Of Kohsuke Kawaguchi
> > Sent: Wednesday, April 15, 2009 11:17 AM
> > To: [hidden email]
> > Subject: Re: Re: hpi:run and executing a maven job
>
> > Brian, I thought your problem is ClassNotFoundException. Are you
> > saying you get this exception when you work on a different plugin?
>
> I'm getting this with maven-plugin from the hudson-1_299 tag,
> not the trunk.  With the trunk, I get the
> ClassNotFoundException.  I switched to try to work from code
> that should be in a known-good state.
>
> The hpi:run problem was resolved by changing to maven 2.0.4
> for the invocation of hpi:run, but I had to add an explicit
> dependency on
> 2.0-beta-7 of the release plugin.  2.0-beta-8 requires 2.0.9
> (or 2.0.6, I forget which, now).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: RE: RE: Re: Re: hpi:run and executing a maven job

blalor
> -----Original Message-----
> From: Spengler, Thomas [mailto:[hidden email]]
> Sent: Wednesday, April 15, 2009 3:08 PM
> To: [hidden email]
> Subject: RE: RE: Re: Re: hpi:run and executing a maven job

> The problem is the JDK you are using.
> I got this error every time, using the JDK6.
> With Jdk5 works.

Ok, but the enforcer plugin forces the build to use JDK6.



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: hpi:run and executing a maven job

Erik Ramfelt
In reply to this post by Kohsuke Kawaguchi
Im using maven 2.0.9 and JDK 1.6. Same maven as I have configured in Hudson.

regards
//Erik

On Wed, Apr 15, 2009 at 5:02 PM, Kohsuke Kawaguchi <[hidden email]> wrote:

> It looks like Maven inside Hudson and Maven outside Hudson (the one
> that you used to launch hpi:run) is interfering.
> Which version of Maven do you use to run hpi:run?
>
> 2009/4/15 Erik Ramfelt <[hidden email]>:
>> Im trying to verify a bug fix for maven jobs in my ci-game plugin. I
>> start it by running "mvn hpi:run -Djetty.port=8100", and create a
>> Maven job that checks out the ci-game source tree. But when I build
>> the job I get a strange error that I can not figure out if its because
>> a bad setup on my machine or not. Could anyone help me out?
>>
>>
>> The ci-game POM looks like this:
>> http://fisheye4.atlassian.com/browse/~raw,r=16903/hudson/trunk/hudson/plugins/ci-game/pom.xml
>>
>> The error is:
>> -----------------------------------------------------
>> At revision 17177
>> no change for https://svn.dev.java.net/svn/hudson/trunk/hudson/plugins/ci-game
>> since the previous build
>> Parsing POMs
>> ERROR: Failed to parse POMs
>> org.apache.maven.embedder.MavenEmbedderException: Cannot lookup
>> required component.
>>        at hudson.maven.MavenEmbedder.start(MavenEmbedder.java:722)
>>        at hudson.maven.MavenUtil.createEmbedder(MavenUtil.java:107)
>>        at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:727)
>>        at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:675)
>>        at hudson.FilePath.act(FilePath.java:552)
>>        at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:425)
>>        at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:315)
>>        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:272)
>>        at hudson.model.Run.run(Run.java:923)
>>        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:234)
>>        at hudson.model.ResourceController.execute(ResourceController.java:93)
>>        at hudson.model.Executor.run(Executor.java:119)
>> Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException:
>> Unable to lookup component
>> 'org.apache.maven.project.MavenProjectBuilder', it could not be
>> started
>>        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339)
>>        at org.codehaus.plexus.embed.Embedder.lookup(Embedder.java:78)
>>        at hudson.maven.MavenEmbedder.start(MavenEmbedder.java:686)
>>        ... 11 more
>> Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException:
>> Error starting component
>>        at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109)
>>        at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
>>        at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
>>        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
>>        ... 13 more
>> Caused by: org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException:
>> Error composing component
>>        at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:33)
>>        at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
>>        at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
>>        ... 16 more
>> Caused by: org.codehaus.plexus.component.composition.CompositionException:
>> Composition failed of field modelInterpolator in object of type
>> org.apache.maven.project.DefaultMavenProjectBuilder because the
>> requirement ComponentRequirement{role='org.apache.maven.project.interpolation.ModelInterpolator',
>> roleHint='null', fieldName='null'} was missing
>>        at org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:154)
>>        at org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
>>        at org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
>>        at org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
>>        at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
>>        ... 18 more
>> Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException:
>> Unable to lookup component
>> 'org.apache.maven.project.interpolation.ModelInterpolator', it could
>> not be created
>>        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
>>        at org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
>>        ... 22 more
>> Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException:
>> Could not instanciate component: role:
>> 'org.apache.maven.project.interpolation.ModelInterpolator',
>> implementation:
>> 'org.apache.maven.project.interpolation.RegexBasedModelInterpolator'
>>        at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77)
>>        at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62)
>>        at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
>>        at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
>>        at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
>>        at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
>>        ... 23 more
>> Caused by: java.lang.NoSuchMethodError:
>> org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
>>        at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63)
>>        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>>        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>>        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>>        at java.lang.Class.newInstance0(Class.java:355)
>>        at java.lang.Class.newInstance(Class.java:308)
>>        at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
>>        ... 27 more
>> Finished: FAILURE
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
>
> --
> Kohsuke Kawaguchi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: hpi:run and executing a maven job

Jesse Glick
In reply to this post by Erik Ramfelt
Erik Ramfelt wrote:
> java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars()Ljava/util/Properties;
> at org.apache.maven.project.interpolation.RegexBasedModelInterpolator.<init>(RegexBasedModelInterpolator.java:63)

Kohsuke claims to have just fixed this in trunk:

https://hudson.dev.java.net/nonav/issues/show_bug.cgi?id=3528


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: hpi:run and executing a maven job

Erik Ramfelt

Great. Thanks for the notification!

Regards
//erik

On Apr 21, 2009 3:21 AM, "Jesse Glick" <[hidden email]> wrote:

Erik Ramfelt wrote: > > java.lang.NoSuchMethodError: org.codehaus.plexus.util.cli.CommandLineUtils.g...

Kohsuke claims to have just fixed this in trunk:

https://hudson.dev.java.net/nonav/issues/show_bug.cgi?id=3528

--------------------------------------------------------------------- To unsubscribe, e-mail: dev...