[
https://issues.jenkins-ci.org/browse/JENKINS-11078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158580#comment-158580
]
kutzi edited comment on JENKINS-11078 at 2/3/12 10:17 AM:
----------------------------------------------------------
Seems to be related to JENKINS-2295 (only for Maven 3 in this case).
Root problem in both cases seems to be that modules are added via profiles
which is something Jenkins still cannot handle in every scenario.
was (Author: kutzi):
Seems to be related to JENKINS-2295 (only for Maven 3 in this case).
Root problem in both cases seems to be that modules are added via profiles
which is something Jenkins still cannot handle.
> NullPointerException in
> udson.maven.Maven3Builder$MavenExecutionListener.recordProjectStarted
> ---------------------------------------------------------------------------------------------
>
> Key: JENKINS-11078
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11078
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Reporter: David Karlsen
> Priority: Critical
>
> {noformat}
> 22:24:15 mavenExecutionResult exceptions not empty
> 22:24:15 message : Internal error: java.lang.NullPointerException
> 22:24:15 cause : null
> 22:24:15 Stack trace :
> 22:24:15 org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> 22:24:15 at
> org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
> 22:24:15 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
> 22:24:15 at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
> 22:24:15 at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:164)
> 22:24:15 at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 22:24:15 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 22:24:15 at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 22:24:15 at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 22:24:15 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 22:24:15 at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 22:24:15 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 22:24:15 at java.lang.Thread.run(Thread.java:662)
> 22:24:15 Caused by: java.lang.NullPointerException
> 22:24:15 at
> hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectStarted(Maven3Builder.java:368)
> 22:24:15 at
> hudson.maven.Maven3Builder$MavenExecutionListener.projectStarted(Maven3Builder.java:358)
> 22:24:15 at
> org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:71)
> 22:24:15 at
> org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
> 22:24:15 at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:78)
> 22:24:15 ... 10 more
> {noformat}
> I have some modules which gets activated by properties (provided as
> buildparameters) - when I activate these with the property it fails with the
> stack trace.
> Note however that if the same modules are activated explicity on the
> commandline with -P it all works ok - so this only happens when activating
> via properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
