问题描述

在将 Java 插件 从版本 3.14 更新到 4.0.

The analyzes of my projects are failing with SonarQube 5.6, after updating the Java Plugin from version 3.14 to 4.0.

在我的 SonarQube 实例中，除其他插件外，我目前有 Findbugs 插件(版本 3.3)和 Cobertura 插件(1.6.3)，它们需要 Java 插件.

In my SonarQube instance, among other plugins, I currently have the Findbugs plugin (version 3.3) and the Cobertura plugin (1.6.3) which require the Java plugin.

查看日志，我收到以下消息:

Looking at the log, I get the following message:

[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.1-build231:sonar (default-cli) 
    on project MyProject: Execution default-cli of goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.1-build231:sonar failed:

    An API incompatibility was encountered while executing org.sonarsource.scanner.maven:sonar-maven-plugin:3.1-build231:sonar: 

    java.lang.NoSuchMethodError:
    org.sonar.plugins.java.api.JavaResourceLocator.findResourceByClassName(Ljava/lang/String;)Lorg/sonar/api/resources/Resource;

...

Caused by: java.lang.NoSuchMethodError: org.sonar.plugins.java.api.JavaResourceLocator.findResourceByClassName(Ljava/lang/String;)Lorg/sonar/api/resources/Resource;
    at org.sonar.plugins.findbugs.FindbugsSensor.analyse(FindbugsSensor.java:108)
    at org.sonar.batch.phases.SensorsExecutor.executeSensor(SensorsExecutor.java:58)
    at org.sonar.batch.phases.SensorsExecutor.execute(SensorsExecutor.java:50)
    at org.sonar.batch.phases.AbstractPhaseExecutor.execute(AbstractPhaseExecutor.java:83)
    at org.sonar.batch.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:192)
    at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:142)
    at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:127)
    at org.sonar.batch.scan.ProjectScanContainer.scan(ProjectScanContainer.java:241)
    at org.sonar.batch.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:236)
    at org.sonar.batch.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:226)
    at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:142)
    at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:127)
    at org.sonar.batch.task.ScanTask.execute(ScanTask.java:47)
    at org.sonar.batch.task.TaskContainer.doAfterStart(TaskContainer.java:86)
    at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:142)
    at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:127)
    at org.sonar.batch.bootstrap.GlobalContainer.executeTask(GlobalContainer.java:106)
    at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:119)
    at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(BatchIsolatedLauncher.java:62)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:60)
    at com.sun.proxy.$Proxy21.execute(Unknown Source)
    at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(EmbeddedScanner.java:240)
    at org.sonarsource.scanner.api.EmbeddedScanner.runAnalysis(EmbeddedScanner.java:151)
    at org.sonarsource.scanner.maven.bootstrap.ScannerBootstrapper.execute(ScannerBootstrapper.java:78)
    at org.sonarsource.scanner.maven.SonarQubeMojo.execute(SonarQubeMojo.java:112)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
    ... 20 more

我应该怎么做才能让我的分析不失败?

What should I do to get my analysis not failing?

推荐答案

SonarQube Java Analyzer 的 4.0 版本对其 API 进行了更改，以保持与SonarQube 5.6 LTS(长期支持)的新 API.

Version 4.0 of the SonarQube Java Analyzer introduced changes in its API, in order to stay aligned with the new API of SonarQube 5.6 LTS (Long Term Support).

不幸的是，这些更改可能会破坏与直接依赖于 Java 分析器的插件的兼容性.如果最新发布的 PMD 和 Checkstyle 插件版本不受影响，那么很遗憾 Findbugs 的版本 3.3 不兼容以及 Cobertura 插件的 1.6.3 版本.

Unfortunately, these changes potentially broke compatibility with plugin directly relying on the Java Analyzer. If last released versions of PMD and Checkstyle plugins are not affected, version 3.3 of the Findbugs is unfortunately not compatible anymore, as well as version 1.6.3 of the Cobertura plugin.

为了解决 Findbugs 的问题，您有以下选择:

In order to solve the issue with Findbugs, you have the following option:

• 更新到 Findbugs 插件的 >= 3.4 版本，该插件目前处于请求反馈期(查看这个帖子)，应该很快就会发布(已确认版本 3.4.2).
• 删除 Findbugs 插件或暂时禁用其规则.

• Update to version >= 3.4 of the Findbugs plugin, which is currently in Request For Feedback period (see this thread), and should be released soon (confirmed with version 3.4.2).
• Remove the Findbugs plugin or temporarily disable its rules.

对于 Cobertura 插件，更新到版本 >= 1.7(需要 LTS 5.6 和 Java 8)，这可以解决问题.应该可以使用 SonarQube UI 获得更新.

For the Cobertura plugin, update to version >= 1.7 (requires LTS 5.6 and Java 8), which solve the issue. The update should be available using the SonarQube UI.