Thor Lange created JENKINS-13090:
------------------------------------
Summary: NoSuchMethodError with the findbugs plugin
Key: JENKINS-13090
URL: https://issues.jenkins-ci.org/browse/JENKINS-13090
Project: Jenkins
Issue Type: Bug
Components: findbugs
Affects Versions: current
Environment: Jenkins 1.455
Reporter: Thor Lange
Assignee: Ulli Hafner
Priority: Critical
Version 4.35 of the findbugs seems to introduce a problem when collecting data
from findbugs running on Maven 2.2.1. The following exception is what we get:
java.lang.NoSuchMethodError:
org.apache.maven.plugin.MojoExecution.getVersion()Ljava/lang/String;
at
hudson.plugins.findbugs.FindBugsReporter.determineFileName(FindBugsReporter.java:191)
at
hudson.plugins.findbugs.FindBugsReporter.perform(FindBugsReporter.java:166)
at
hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:304)
at hudson.maven.Maven2Builder.postExecute(Maven2Builder.java:155)
at hudson.maven.MavenBuilder$Adapter.postExecute(MavenBuilder.java:310)
at
hudson.maven.agent.PluginManagerInterceptor$1MojoIntercepterImpl.callPost(PluginManagerInterceptor.java:170)
at
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:183)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
It seems to be introduced by the commit set fixing JENKINS-12853:
https://github.com/jenkinsci/findbugs-plugin/commit/2d80d625949524a81794ae0b4249872f94feb556
Downgrading to the previous version 4.34 makes the exception go away.
--
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
