ERROR: Processing failed due to a bug in the code.

[Jeff Mutonho]

Hi
I downloaded and installed  the 1.240  version on Tomcat.I'm trying to do a build for a maven2 project but Hudson is dying with the following error message:

At revision 1111
no revision recorded for https://svn.server.co.za/sentium/trunk/src in the previous build
Parsing POMs
ERROR: Processing failed due to a bug in the code. Please report thus to [hidden email]
java.lang.NullPointerException
    at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:684)
    at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:633)
    at hudson.FilePath.act(FilePath.java:319)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:383)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:284)
    at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:231)
    at hudson.model.Run.run(Run.java:786)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:204)
    at hudson.model.ResourceController.execute(ResourceController.java:70)
    at hudson.model.Executor.run(Executor.java:88)
project=hudson.maven.MavenModuleSet@11d20d3[SSOManager Build]
project.getModules()=[]
project.getRootModule()=null
FATAL: null
java.lang.NullPointerException
    at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:684)
    at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:633)
    at hudson.FilePath.act(FilePath.java:319)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:383)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:284)
    at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:231)
    at hudson.model.Run.run(Run.java:786)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:204)
    at hudson.model.ResourceController.execute(ResourceController.java:70)
    at hudson.model.Executor.run(Executor.java:88)


 The maven project builds without any issues when I do the build from the command line , so its not a pom misconfiguration.



 

--

"Don't take the name of root in vain."

Jeff Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042

[Jeff Mutonho]

On Fri, Aug 1, 2008 at 8:52 AM, Jeff Mutonho <[hidden email]> wrote:

Hi
I downloaded and installed  the 1.240  version on Tomcat.I'm trying to do a build for a maven2 project but Hudson is dying with the following error message:

At revision 1111
no revision recorded for https://svn.server.co.za/sentium/trunk/src in the previous build
Parsing POMs
ERROR: Processing failed due to a bug in the code. Please report thus to [hidden email]
java.lang.NullPointerException
    at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:684)
    at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:633)
    at hudson.FilePath.act(FilePath.java:319)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:383)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:284)
    at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:231)
    at hudson.model.Run.run(Run.java:786)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:204)
    at hudson.model.ResourceController.execute(ResourceController.java:70)
    at hudson.model.Executor.run(Executor.java:88)
project=hudson.maven.MavenModuleSet@11d20d3[SSOManager Build]
project.getModules()=[]
project.getRootModule()=null
FATAL: null
java.lang.NullPointerException
    at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:684)
    at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:633)
    at hudson.FilePath.act(FilePath.java:319)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:383)
    at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:284)
    at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:231)
    at hudson.model.Run.run(Run.java:786)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:204)
    at hudson.model.ResourceController.execute(ResourceController.java:70)
    at hudson.model.Executor.run(Executor.java:88)


 The maven project builds without any issues when I do the build from the command line , so its not a pom misconfiguration.



 

--

Hi guys. Anyone got an idea on this?I'm still battling to figure out why I'm getting this NPE from Hudson




--

"Don't take the name of root in vain."

Jeff Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042

[Kohsuke Kawaguchi]

Looks like this is caused by the missing Maven configuration.
Go to the job configuration and you should see an error.

I added an error check on 1.244 to handle this more gracefully.

Jeff Mutonho wrote:

> On Fri, Aug 1, 2008 at 8:52 AM, Jeff Mutonho <[hidden email]> wrote:
>
>> Hi
>> I downloaded and installed  the 1.240<https://hudson.dev.java.net/files/documents/2402/105836/hudson.war>
>> version on Tomcat.I'm trying to do a build for a maven2 project but Hudson
>> is dying with the following error message:
>>
>> At revision 1111
>> no revision recorded for https://svn.server.co.za/sentium/trunk/src in the
>> previous build
>> Parsing POMs
>> ERROR: Processing failed due to a bug in the code. Please report thus to
>> [hidden email]
>> java.lang.NullPointerException
>>     at
>> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:684)
>>     at
>> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:633)
>>     at hudson.FilePath.act(FilePath.java:319)
>>     at
>> hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:383)
>>     at
>> hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:284)
>>     at
>> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:231)
>>     at hudson.model.Run.run(Run.java:786)
>>     at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:204)
>>     at hudson.model.ResourceController.execute(ResourceController.java:70)
>>     at hudson.model.Executor.run(Executor.java:88)
>> project=hudson.maven.MavenModuleSet@11d20d3[SSOManager Build]
>> project.getModules()=[]
>> project.getRootModule()=null
>> FATAL: null
>> java.lang.NullPointerException
>>     at
>> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:684)
>>     at
>> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:633)
>>     at hudson.FilePath.act(FilePath.java:319)
>>     at
>> hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:383)
>>     at
>> hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:284)
>>     at
>> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:231)
>>     at hudson.model.Run.run(Run.java:786)
>>     at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:204)
>>     at hudson.model.ResourceController.execute(ResourceController.java:70)
>>     at hudson.model.Executor.run(Executor.java:88)
>>
>>
>>  The maven project builds without any issues when I do the build from the
>> command line , so its not a pom misconfiguration.
>>
>>
>>
>>
>>
>> --
>>
>>
>>
>
> Hi guys. Anyone got an idea on this?I'm still battling to figure out why I'm
> getting this NPE from Hudson
>
>
>
>

--
Kohsuke Kawaguchi
Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/

[Jeff Mutonho]

On Tue, Aug 5, 2008 at 3:56 AM, Kohsuke Kawaguchi <[hidden email]> wrote:

Looks like this is caused by the missing Maven configuration.
Go to the job configuration and you should see an error.

I added an error check on 1.244 to handle this more gracefully.

I do not understand what I could be missing as I have configured the M2_HOME correctly.I've attached these screen shots for my configuration and the error

By the way , I've upgraded  to the 1.244 version.


--

"Don't take the name of root in vain."

Jeff Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042

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

[Jeff Mutonho]

On Tue, Aug 5, 2008 at 4:55 PM, Jeff Mutonho <[hidden email]> wrote:

On Tue, Aug 5, 2008 at 3:56 AM, Kohsuke Kawaguchi <[hidden email]> wrote:

Looks like this is caused by the missing Maven configuration.
Go to the job configuration and you should see an error.

I added an error check on 1.244 to handle this more gracefully.

I do not understand what I could be missing as I have configured the M2_HOME correctly.I've attached these screen shots for my configuration and the error

By the way , I've upgraded  to the 1.244 version.

--

Hi guys. I'm really not demanding a response , but my builds have completely come to halt by this and ANY help will be greatly appreciated.I thought perhaps posting those screen shots would help explain the problem.
Thanks

[Kohsuke Kawaguchi]

Jeff Mutonho wrote:

> On Tue, Aug 5, 2008 at 4:55 PM, Jeff Mutonho <[hidden email]> wrote:
>
>>
>>
>> On Tue, Aug 5, 2008 at 3:56 AM, Kohsuke Kawaguchi <
>> [hidden email]> wrote:
>>
>>>
>>> Looks like this is caused by the missing Maven configuration.
>>> Go to the job configuration and you should see an error.
>>>
>>> I added an error check on 1.244 to handle this more gracefully.
>>>
>>>
>> I do not understand what I could be missing as I have configured the
>> M2_HOME correctly.I've attached these screen shots for my configuration and
>> the error
>>
>> By the way , I've upgraded  to the 1.244 version.

See the error message and go to the system configuration page and tell
Hudson where your Maven is.

Hudson doesn't look at M2_HOME, but come to think of it, looking for
this environment variable as a part of the fallback sounds like a good
error recovery behavior for Hudson.


--
Kohsuke Kawaguchi
Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/

[Jeff Mutonho]

On Thu, Aug 7, 2008 at 2:31 AM, Kohsuke Kawaguchi <[hidden email]> wrote:

Jeff Mutonho wrote:

On Tue, Aug 5, 2008 at 4:55 PM, Jeff Mutonho <[hidden email]> wrote:

On Tue, Aug 5, 2008 at 3:56 AM, Kohsuke Kawaguchi <
[hidden email]> wrote:

Looks like this is caused by the missing Maven configuration.
Go to the job configuration and you should see an error.

I added an error check on 1.244 to handle this more gracefully.

I do not understand what I could be missing as I have configured the
M2_HOME correctly.I've attached these screen shots for my configuration and
the error

By the way , I've upgraded  to the 1.244 version.

See the error message and go to the system configuration page and tell Hudson where your Maven is.

I've gone to the job configuration and I still see the error message under Maven Version , saying "Hudson needs to know where your Maven2 is installed.Please do so from the system configuration"

But I have configured the Maven2 location from the  http://localhost:8080/hudson/configure page  and added the following :

name                    : Apache-maven-2.0.8

MAVEN_HOME    : C:\devenv\apache-maven-2.0.8

After that clicked on the Save button at the bottom.

I even restarted my Tomcat thinking that the configuration will only take effect after a restart, but the error won't go away.
I also noticed that under "List of Maven installations on this system. Both maven 1 and 2 are supported."  , there nothing listed even after I Save the above MAVEN_HOME configuration.



"Don't take the name of root in vain."

Jeff Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042

[Kohsuke Kawaguchi]

That sounds like the problem we fixed in 1.242.

Perhaps you tried to save Maven configuration when you were using that version?

2008/8/7 Jeff Mutonho <[hidden email]>:

>
>
> On Thu, Aug 7, 2008 at 2:31 AM, Kohsuke Kawaguchi
> <[hidden email]> wrote:
>>
>> Jeff Mutonho wrote:
>>>
>>> On Tue, Aug 5, 2008 at 4:55 PM, Jeff Mutonho <[hidden email]> wrote:
>>>
>>>>
>>>>
>>>> On Tue, Aug 5, 2008 at 3:56 AM, Kohsuke Kawaguchi <
>>>> [hidden email]> wrote:
>>>>
>>>>>
>>>>> Looks like this is caused by the missing Maven configuration.
>>>>> Go to the job configuration and you should see an error.
>>>>>
>>>>> I added an error check on 1.244 to handle this more gracefully.
>>>>>
>>>>>
>>>> I do not understand what I could be missing as I have configured the
>>>> M2_HOME correctly.I've attached these screen shots for my configuration
>>>> and
>>>> the error
>>>>
>>>> By the way , I've upgraded  to the 1.244 version.
>>
>> See the error message and go to the system configuration page and tell
>> Hudson where your Maven is.
>>
>
> I've gone to the job configuration and I still see the error message under
> Maven Version , saying "Hudson needs to know where your Maven2 is
> installed.Please do so from the system configuration"
>
> But I have configured the Maven2 location from the
> http://localhost:8080/hudson/configure page  and added the following :
>
> name                    : Apache-maven-2.0.8
>
> MAVEN_HOME    : C:\devenv\apache-maven-2.0.8
>
> After that clicked on the Save button at the bottom.
>
> I even restarted my Tomcat thinking that the configuration will only take
> effect after a restart, but the error won't go away.
> I also noticed that under "List of Maven installations on this system. Both
> maven 1 and 2 are supported."  , there nothing listed even after I Save the
> above MAVEN_HOME configuration.
>
>
>
> "Don't take the name of root in vain."
>
> Jeff Mutonho
> Cape Town
> South Africa
>
> GoogleTalk : ejbengine
> Skype : ejbengine
> Registered Linux user number 366042
>

--
Kohsuke Kawaguchi

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

[Jeff Mutonho]

On Thu, Aug 7, 2008 at 5:01 PM, Kohsuke Kawaguchi <[hidden email]> wrote:

That sounds like the problem we fixed in 1.242.

Perhaps you tried to save Maven configuration when you were using that version?

I've finally gone past this issue... I ended up having to clear anything Hudson related in my Tomcat and installed the latest stable release.
Thanks for all the help.


"Don't take the name of root in vain."

Jeff Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042