[
https://issues.jenkins-ci.org/browse/JENKINS-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
evernat resolved JENKINS-2807.
------------------------------
Resolution: Duplicate
Yes it seems like a duplicate of JENKINS-1454, so resolving as duplicate.
Please reopen if needed.
> Hudson FATAL error when switching JDK (m2 support)
> --------------------------------------------------
>
> Key: JENKINS-2807
> URL: https://issues.jenkins-ci.org/browse/JENKINS-2807
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: lacostej
>
> How to reproduce:
> 1- have a build with a profile that triggers different modules based on jdk.
> 2- build
> 3- switch JDK so that another module is built
> Expected:
> * build passes
> Got:
> booom:
> java.lang.AssertionError: reporters.get($GROUPID:$ARTIFACTID)==null.
> reporters={
> LIST OF REPORTERS}
> at
> hudson.maven.MavenModuleSetBuild$Builder.postModule(MavenModuleSetBuild.java:572)
> at
> hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:284)
> at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:242)
> at
> org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:45)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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:135)
> at hudson.maven.MavenBuilder.call(MavenBuilder.java:139)
> at
> hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:542)
> at
> hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:488)
> at hudson.remoting.UserRequest.perform(UserRequest.java:69)
> at hudson.remoting.UserRequest.perform(UserRequest.java:23)
> at hudson.remoting.Request$2.run(Request.java:213)
> 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)
> $GROUPID:$ARTIFACTID matches the module now newly triggered, (was never
> triggered before)
> Here's a code snippet that shows the m2 profile module selection based on JDK.
> <profiles>
> <profile>
> <id>jdk14</id>
> <activation>
> <jdk>1.4</jdk>
> </activation>
> <modules>
> <module>X-14</module>
> </modules>
> </profile>
> <profile>
> <id>jdk15</id>
> <activation>
> <jdk>1.5</jdk>
> </activation>
> <modules>
> <module>X-14</module>
> </modules>
> </profile>
> <profile>
> <id>jdk16</id>
> <activation>
> <jdk>1.6</jdk>
> </activation>
> <modules>
> <module>X-16</module>
> </modules>
> </profile>
> </profiles>
--
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
