-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: All
-
Powered by SuggestiMate
I have a big maven 2 multi-project that fails at the end.
I'm using Hudson ver. 1.189 (running under Java 1.5 and Tomcat 6), and Maven v.
2.0.8
Here is the stack trace:
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] reporters.get(org.ecc.helios:helios-server)==null.
reporters=
proxies=
{org.ecc.helios:helios-packaging-root=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@1963c81}[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.AssertionError: reporters.get(org.ecc.helios:helios-server)==null.
reporters=
proxies=
{org.ecc.helios:helios-packaging-root=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@1963c81} at
hudson.maven.MavenModuleSetBuild$Builder.postModule(MavenModuleSetBuild.java:488)
at hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:261)
at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:225)
at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:45)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
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:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:97)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:129)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:458)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:404)
at hudson.remoting.UserRequest.perform(UserRequest.java:69)
at hudson.remoting.UserRequest.perform(UserRequest.java:23)
at hudson.remoting.Request$2.run(Request.java:200)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
- backlog.txt
- 0.4 kB
- log.txt
- 56 kB
- depends on
-
JENKINS-906 Maven 2 build failure
-
- Reopened
-
- is blocking
-
JENKINS-6530 Assertion in MavenModuleSetBuild for aggregator POM with modules
-
- Open
-
-
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
-
- is duplicated by
-
JENKINS-2807 Hudson FATAL error when switching JDK (m2 support)
-
- Reopened
-
-
JENKINS-6567 CLONE -Maven2: AssertionError: reporters.get == null
-
- Resolved
-
[JENKINS-1454] Maven2: AssertionError: reporters.get == null
Created an attachment (id=196)
A Maven2 project that triggers the 'assertionError' bug
I've just attached a Maven2 project that triggers the assertion error.
This project shows an error that occurs if a module is included by a profile
that was activated by a property.
To see the error, create a new Maven2 job in Hudson configured like this:
Root POM: hudson-assertionError-test/pom.xml
Goals : install -X -Dinclude-optional
(Or just copy the job configuration file from
'hudson-assertionError-test.zip/hudson-assertionError-test/hudson-job-config/config.xml')
When you tell Hudson to build it, this error will be printed:
–
started
Parsing POMs
[hudson-assertionError-test] $ java -cp
E:\apps\apache-tomcat-6.0.16\webapps\hudson\WEB-INF\lib\maven-agent-1.199.jar;E:\apps\apache-maven-2.0.8\boot\classworlds-1.1.jar
hudson.maven.agent.Main E:\apps\apache-maven-2.0.8
E:\apps\apache-tomcat-6.0.16\webapps\hudson\WEB-INF\lib\remoting-1.199.jar
E:\apps\apache-tomcat-6.0.16\webapps\hudson\WEB-INF\lib\maven-interceptor-1.199.jar
???channel started
+ Error stacktraces are turned on.
Maven version: 2.0.8
Java version: 1.5.0_07
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
[...]
[INFO] ------------------------------------------------------------------------
[INFO] Building module 2 (OPTIONAL)
[INFO] task-segment: [install]
[INFO] ------------------------------------------------------------------------
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-resources-plugin:2.2:resources' -->
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO]
reporters.get(com.orgecc.test.hudson:hudson-assertionError-test-module-2)==null.
reporters=
proxies=
{com.orgecc.test.hudson:hudson-assertionError-test-root=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@a76306, com.orgecc.test.hudson:hudson-assertionError-test-module-1=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@1563e06}[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
java.lang.AssertionError:
reporters.get(com.orgecc.test.hudson:hudson-assertionError-test-module-2)==null.
reporters=
proxies=
{com.orgecc.test.hudson:hudson-assertionError-test-root=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@a76306, com.orgecc.test.hudson:hudson-assertionError-test-module-1=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@1563e06} at
hudson.maven.MavenModuleSetBuild$Builder.postModule(MavenModuleSetBuild.java:506)
at hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:261)
at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:225)
at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:45)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:97)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:129)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:476)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:422)
at hudson.remoting.UserRequest.perform(UserRequest.java:69)
at hudson.remoting.UserRequest.perform(UserRequest.java:23)
at hudson.remoting.Request$2.run(Request.java:200)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
[INFO] ------------------------------------------------------------------------
–
I can confirm the problem exactly as described above. As a workaround, I've
added by hand the required modules (as opposed to include them using a profile)
in the local svn checkout.
Update the summary to clarify that this problem is specific to Maven2 jobs
This error occurs because the hudson parsing of the goals configuration option
is not as complete as the maven CLI. For example: "-Pprofilename" does not work
but "-P profilename" does work while on the CLI both work.
Code changed in hudson
User: : kohsuke
Path:
trunk/hudson/main/core/src/main/java/hudson/maven/MavenModuleSet.java
http://fisheye4.cenqua.com/changelog/hudson/?cs=15165
Log:
JENKINS-1454 Improved the CLI option parsing to recognize "-Px,y,z" as profiles. This will be in 1.283.
Code changed in hudson
User: : kohsuke
Path:
trunk/hudson/main/core/src/main/java/hudson/maven/MavenEmbedder.java
trunk/hudson/main/core/src/main/java/hudson/maven/MavenModuleSet.java
trunk/hudson/main/core/src/main/java/hudson/maven/MavenModuleSetBuild.java
trunk/hudson/main/core/src/main/java/hudson/maven/MavenUtil.java
trunk/hudson/main/core/src/main/java/hudson/tasks/Maven.java
trunk/www/changelog.html
http://fisheye4.cenqua.com/changelog/hudson/?cs=15169
Log:
[FIXED JENKINS-1454]
Handled the property-based activation correctly. Will be in 1.283.
Hi guys, sorry to reopen this.
However, I'm trying to launch a build using this command:
-B -U -e clean install
And I get this:
INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] reporters.get(com.$COMPANY.$TESTTOOL.test:com.$COMPANY.$TESTTOOL.$PROJECT.tests)==null. reporters=
proxies=
{com.$COMPANY.tools:$TESTTOOL-test-launcher=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@180ce9c}[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.AssertionError: reporters.get(com.$COMPANY.$TESTTOOL.test:com.$COMPANY.$TESTTOOL.$PROJECT.tests)==null. reporters=
proxies=
{com.$COMPANY.tools:$TESTTOOL-test-launcher=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@180ce9c} at hudson.maven.MavenModuleSetBuild$Builder.postModule(MavenModuleSetBuild.java:718)
at hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:304)
at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:262)
at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:68)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at com.$COMPANY.maven2.plugins.mojos.$TESTTOOLAutomationMojo.createEclipseProject($TESTTOOLAutomationMojo.java:182)
at com.$COMPANY.maven2.plugins.mojos.$TESTTOOLAutomationMojo.prepareTest($TESTTOOLAutomationMojo.java:160)
at com.$COMPANY.maven2.plugins.mojos.$TESTTOOLAutomationMojo.execute($TESTTOOLAutomationMojo.java:144)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
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:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:165)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:159)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:688)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:632)
at hudson.remoting.UserRequest.perform(UserRequest.java:104)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Thu Feb 04 16:44:29 CET 2010
[INFO] Final Memory: 19M/497M
[INFO] ------------------------------------------------------------------------
I'll attach the pom launched and the full log
Hi,
I am also facing a similar issue.
The parent pom of my project defines couple of profiles.
I have configured the project as a parametrized build to pass a parameter "deploy" for activating the profiles.
I am using the command "-Ddeploy=${deploy} clean install"
The build runs fine with the default activated profile.
The build also works fine when i directly pass the parameter from the configured command like "-Ddeploy=systemtest clean install"
But when I select the parameter from Hudson to activate other profile(systemtest) then the build fails showing the below error:-
Executing Maven: -B -f D:\.hudson\jobs\platform_backend_server_CI\workspace\server\pom.xml clean install -Ddeploy=systemtest
INFO 090210-15:47:13 Scanning for projects...
INFO 090210-15:47:13 ------------------------------------------------------------------------
INFO 090210-15:47:13 Building server-facade Maven Webapp
INFO 090210-15:47:13 task-segment: [clean, install]
INFO 090210-15:47:13 ------------------------------------------------------------------------
INFO 090210-15:47:14 ------------------------------------------------------------------------
ERROR 090210-15:47:14 FATAL ERROR
INFO 090210-15:47:14 ------------------------------------------------------------------------
INFO 090210-15:47:14 reporters.get(server:facade-systemtest)==null. reporters=
proxies=
{server:facade-default=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@ee9f13}INFO 090210-15:47:14 ------------------------------------------------------------------------
INFO 090210-15:47:14 Trace
java.lang.AssertionError: reporters.get(server:facade-systemtest)==null. reporters=
proxies=
{server:facade-default=hudson.maven.MavenModuleSetBuild$Builder$FilterImpl@ee9f13} at hudson.maven.MavenModuleSetBuild$Builder.postModule(MavenModuleSetBuild.java:718) [na:na]
at hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:304) [na:na]
at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:262) [na:na]
at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:68) [maven-interceptor-1.337.jar:na]
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) [maven-2.2.1-uber.jar:2.2.1]
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) [maven-2.2.1-uber.jar:2.2.1]
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) [maven-2.2.1-uber.jar:2.2.1]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [na:1.6.0_17]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [na:1.6.0_17]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [na:1.6.0_17]
at java.lang.reflect.Method.invoke(Method.java:597) [na:1.6.0_17]
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [classworlds-1.1.jar:1.1]
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [classworlds-1.1.jar:1.1]
at hudson.maven.agent.Main.launch(Main.java:165) [maven-agent-1.337.jar:na]
at hudson.maven.MavenBuilder.call(MavenBuilder.java:159) [na:na]
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:688) [na:na]
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:632) [na:na]
at hudson.remoting.UserRequest.perform(UserRequest.java:104) [remoting-1.337.jar:na]
at hudson.remoting.UserRequest.perform(UserRequest.java:48) [remoting-1.337.jar:na]
at hudson.remoting.Request$2.run(Request.java:270) [remoting-1.337.jar:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [na:1.6.0_17]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [na:1.6.0_17]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [na:1.6.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_17]
at java.lang.Thread.run(Thread.java:619) [na:1.6.0_17]
INFO 090210-15:47:14 ------------------------------------------------------------------------
INFO 090210-15:47:14 Total time: 1 second
INFO 090210-15:47:14 Finished at: Tue Feb 09 15:47:14 CET 2010
INFO 090210-15:47:14 Final Memory: 7M/13M
INFO 090210-15:47:14 ------------------------------------------------------------------------
I am hoping for a quick fix of this issue.
Thanks
I do confirm, in our chain we have in the 2nd job maven target: cobertura:cobertura ${mvn_opts}
And the ${mvn_opts} is set in the 1st job of the chain with maven_opts="-P PROFILE1"
The result:
[INFO] Preparing cobertura:cobertura
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] reporters.get(com.bobo....:module1)==null. reporters=
proxies=
{com.bobo....:ROOT=hudson.maven.AbstractMavenBuilder$FilterImpl@89371a}[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.AssertionError: reporters.get(com.bobo....:module1)==null. reporters=
proxies=
{com.bobo....:ROOT=hudson.maven.AbstractMavenBuilder$FilterImpl@89371a} at hudson.maven.Maven2Builder.postModule(Maven2Builder.java:126)
at hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:340)
at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:296)
at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:68)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
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 hudson.maven.agent.Main.launch(Main.java:185)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:153)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:79)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:55)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13 seconds
[INFO] Finished at: Wed Jan 30 14:59:27 CET 2013
[INFO] Final Memory: 39M/95M
[INFO] ------------------------------------------------------------------------
En attente que Jenkins finisse de récupérer les données
channel stopped
Finished: FAILURE
Note: running mvn from the command line works fine.