SonarQube version: 7.9.1 LTS
Sonar-Findbugs-plugin: 3.11.0
Jenkins job:
JDK: 1.8_92
Sonar Scanner 4.0.0
During the post-build Sonar scanner analysis I am seeing an error related to the Findbugs plugin
The following errors occurred during analysis:
huh
java.lang.ClassNotFoundException
At edu.umd.cs.findbugs.ba.ch.Subtypes2$SupertypeQueryResults.containsType(Subtypes2.java:108)
At edu.umd.cs.findbugs.ba.ch.Subtypes2.isSubtype0(Subtypes2.java:490)
At edu.umd.cs.findbugs.ba.ch.Subtypes2.isSubtype(Subtypes2.java:407)
At edu.umd.cs.findbugs.detect.FindUnsatisfiedObligation$MethodChecker.reportWarning(FindUnsatisfiedObligation.java:328)
At edu.umd.cs.findbugs.detect.FindUnsatisfiedObligation$MethodChecker.analyzeMethod(FindUnsatisfiedObligation.java:277)
At edu.umd.cs.findbugs.detect.FindUnsatisfiedObligation.visitMethodCFG(FindUnsatisfiedObligation.java:159)
At edu.umd.cs.findbugs.bcel.CFGDetector.visitClass(CFGDetector.java:93)
At edu.umd.cs.findbugs.detect.FindUnsatisfiedObligation.visitClass(FindUnsatisfiedObligation.java:139)
At edu.umd.cs.findbugs.FindBugs2.analyzeApplication(FindBugs2.java:1080)
At edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:281)
At org.sonar.plugins.findbugs.FindbugsExecutor$FindbugsTask.call(FindbugsExecutor.java:235)
At java.util.concurrent.FutureTask.run(FutureTask.java:266)
At java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
At java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
At java.lang.Thread.run(Thread.java:745)
The following classes needed for analysis were missing:
scala.runtime.AbstractFunction1
scala.Serializable
scala.runtime.AbstractFunction0
scala.runtime.AbstractFunction1$mcVI$sp
com.marketo.locatorservice.client.LocatorServiceClientConfig
scala.Product
scala.runtime.AbstractFunction6
org.apache.commons.pool.PoolableObjectFactory
scala.Predef$
...
This error is only occurring on this job on the Jenkins server, other analyses do not have this exception.
Initially was getting this error with SonarQube Scanner 2.9, but also occurs with latest Scanner version 4.0.0
The analysis still completes successfully, so it isn’t blocking the job.
Do the developers just need to defined the listed missing classes in their source code?