I’m suggesting you look into whether or not you’re using the latest versions of these plugins (the Plugin Version Matrix may help), and if that doesn’t help, try selectively installing/uninstalling the plugins to see if it affects the presence of the error.
So I Looked at the plugin Matrix and other than Checkstyle, all seems to be current. Is there any specific one you were referring to which seemd old?
| Current | Expected | Action Needed | Plugin Path |
|---|---|---|---|
| checkstyle-sonar-plugin-10.6.0.jar | 10.12.3 | Yes | GitHub - checkstyle/sonar-checkstyle: Support on Checkstyle in SonarQube. Officially transfered from GitHub - SonarQubeCommunity/sonar-checkstyle: Support on Checkstyle in SonarQube |
| sonar-groovy-plugin-1.8.jar | 1.8 | NO | GitHub - Inform-Software/sonar-groovy: SonarQube plugin for Groovy |
| sonar-pmd-plugin-3.4.0.jar | 3.4.0 | NO | GitHub - jborgers/sonar-pmd:  PMD Plugin for SonarQube |
| java-i18n-rules-0.1.0.jar | 0.1.0 | NO | GitHub - edwinyangzh/sonar-java-i18n-checks: Java I18N code analyzer plugin for SonarQube |
| sonar-findbugs-plugin-4.2.3.jar | 4.2.3 | NO | GitHub - spotbugs/sonar-findbugs: SpotBugs plugin for SonarQube |
| sonar-jdepend-plugin-1.1.1.jar | 1.1.1 | NO | GitHub - willemsrb/sonar-jdepend-plugin: Sonar plugin for jDepend |
| sonar-yaml-plugin-1.7.0.jar | 1.7.0 | NO | GitHub - sbaudoin/sonar-yaml: SonarQube plugin to analyze YAML files |
No, it was just general advice.
So, as mentioned before, time to selectively uninstall/reinstall to see if you can pinpoint one plugin being the issue!
Hello,
For a start, you can try removing sonar-java-i18n-checks & sonar-jdepend-plugin because I have all other plugins in their latest available version installed in my instance of Sonarqube running v9.9.2 and I don’t seem to face any issues during a grade build.
Thanks,
Aravind
1 Like
GM this seems to solved the issue and I am able to run the scans now. I started getting this notification (attaching screenshot). Can you please let me know what that means? Is it saying that going forward Sonar will not support the external/third party plugins?
Glad your initial issue is resolved.
If you don’t know what an exporter is, you don’t have to worry about it. 
It’s a very old SonarQube feature that allows you to export the configuration of third-party analyzers (like Findbugs) based on what is in your Quality profile (belonging to those third-party analyzers, such as rules provided in the Findbugs plugin).
It does not mean that Sonar will stop supporting third-party plugins.
Hi Colin,
I have used hasSemantic() in my custom rules plugin and I see after upgrading the sonar-java-version the hasSemantic() has been deprecated. What is the alternative for this deprecation ?
Hey @qwert
Please raise a new thread, instead of bumping an old, completed one.