-
Bug
-
Resolution: Not A Defect
-
Blocker
-
Jenkins ver. 1.532.2-SNAPSHOT (rc-01/13/2014 23:54 GMT-kohsuke)
Maven Project Plugin ver 2.1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5:36.275s
[INFO] Finished at: Thu Feb 06 19:32:25 CET 2014
[INFO] Final Memory: 41M/227M
[INFO] ------------------------------------------------------------------------
Waiting for Jenkins to finish collecting data
[JENKINS] Archiving /repo/eis-jenkins-lmr-radiosw/slave/workspace/monitoring-beacon-jenkins-javadoc-plugin@2/pom.xml to org.jenkins-ci.plugins/javadoc/1.2-SNAPSHOT/javadoc-1.2-SNAPSHOT.pom
[JENKINS] Archiving /repo/eis-jenkins-lmr-radiosw/slave/workspace/monitoring-beacon-jenkins-javadoc-plugin@2/target/javadoc.hpi to org.jenkins-ci.plugins/javadoc/1.2-SNAPSHOT/javadoc-1.2-SNAPSHOT.hpi
[JENKINS] Archiving /repo/eis-jenkins-lmr-radiosw/slave/workspace/monitoring-beacon-jenkins-javadoc-plugin@2/target/javadoc.jar to org.jenkins-ci.plugins/javadoc/1.2-SNAPSHOT/javadoc-1.2-SNAPSHOT.jar
FATAL: hudson.maven.MavenBuild.isInProgress()Z
java.lang.NoSuchMethodError: hudson.maven.MavenBuild.isInProgress()Z
at hudson.maven.MavenBuild.access$700(MavenBuild.java:94)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:621)
at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:839)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566)
at hudson.model.Run.execute(Run.java:1665)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
This is probably a (in)compability issue between 1.532.2 LTS and maven-plugin >=2.1.
I had the same issue using 1.532.2 LTS and maven-plugin 2.3.
Downgrading maven-plugin to the 1.532.2-LTS-supplied 2.0 removed the error.
There's also a StackOverflow entry suggesting it's a compatibility issue helps: http://stackoverflow.com/questions/20760039/build-issues-in-jenkins