-
Bug
-
Resolution: Duplicate
-
Critical
-
None
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
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.
- duplicates
-
JENKINS-2295 Jenkins cannot handle modules added by profiles - if profile is not activated via '-P' (was: Assertion in MavenModuleSetBuild for aggregator POM with modules provided by profile)
- Reopened