-
Bug
-
Resolution: Fixed
-
Major
-
None
00:00:02.778 ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com 00:00:02.780 java.lang.NullPointerException 00:00:02.780 at jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties(PomPropertiesFinder.java:38) 00:00:02.780 at jenkins.plugins.maveninfo.extractor.MavenInfoExtractor.extract(MavenInfoExtractor.java:58) 00:00:02.780 at jenkins.plugins.maveninfo.extractor.MavenInfoEnvironment.tearDown(MavenInfoEnvironment.java:42) 00:00:02.780 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:852) 00:00:02.780 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) 00:00:02.780 at hudson.model.Run.execute(Run.java:1677) 00:00:02.780 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) 00:00:02.780 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:00:02.780 at hudson.model.Executor.run(Executor.java:231) 00:00:02.780 project=hudson.maven.MavenModuleSet@4c7b39a1[build-realtimedlp-trunk] 00:00:02.781 project.getModules()=[hudson.maven.MavenModule@11b9981a[build-realtimedlp-trunk/com.shn.dlp:realtimedlp][build-realtimedlp-trunk/com.shn.dlp:realtimedlp][relativePath:]] 00:00:02.781 project.getRootModule()=hudson.maven.MavenModule@11b9981a[build-realtimedlp-trunk/com.shn.dlp:realtimedlp][build-realtimedlp-trunk/com.shn.dlp:realtimedlp][relativePath:] 00:00:02.781 FATAL: null 00:00:02.781 java.lang.NullPointerException 00:00:02.781 at jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties(PomPropertiesFinder.java:38) 00:00:02.781 at jenkins.plugins.maveninfo.extractor.MavenInfoExtractor.extract(MavenInfoExtractor.java:58) 00:00:02.781 at jenkins.plugins.maveninfo.extractor.MavenInfoEnvironment.tearDown(MavenInfoEnvironment.java:42) 00:00:02.781 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:852)
If happens under various conditions, sometimes even when the pom.xml files are not updated (though it might have been updated in one of the binary dependencies).
One such conditions is to use a property to set the version number of a dependency but have a typo in the property name. The Maven Info Plugin does not handle the problem gracefully and throws a null pointer exception. I suspect having version conflicts in the dependency tree can sometime trigger the issue as well.
