-
Bug
-
Resolution: Unresolved
-
Minor
-
None
We have Jenkins ver. 1.651.3 and I suspect it's the maven-plugin (2.12) that is occasionally causing such errors in a build. A simple rebuild no longer runs into the same problem.
Parsing POMs Downloaded artifact ... Downloaded artifact ... Downloaded artifact ... Discovered a new module <groupId>:<artifactId> <directory> ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.UnsupportedOperationException at java.util.AbstractMap.put(AbstractMap.java:209) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:1009) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) project=hudson.maven.MavenModuleSet@193d5d2e[<Jenkins_Job_Name>] project.getModules()=[] project.getRootModule()=null FATAL: null java.lang.UnsupportedOperationException at java.util.AbstractMap.put(AbstractMap.java:209) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:1009) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410
I have found similar error reports but mostly related to the release plugin or Maven 2. Our job is a 'standard' Maven project running mvn3.
Any ideas in what circumstance project.getRootModule() can be null?