We also ran into this issue, for multiple product teams, after an upgrade from v10.2 to v10.5. Today we’ve upgrade to v10.6, but the issue seems to persist for multiple teams.
Attached a recent log file showing that we’re running Azure DevOps task v6.1, Java 17 and use SonarQube server 10.6.0.
logs.txt (11.9 KB)
Hey @AdeZwart
While this is another java.lang.NoClassDefFoundError error, it looks to be different from the one that was affecting v10.5, so I’ve split this into a new thread.
Could you add sonar.verbose=true to the analysis parameters are run again (and provide the logs)? Do you face this issue with other Scanners than the Scanner for .NET (the SonarScanner CLI, for example)?
Please also try disabling the Analyzers loading optimization option, to see if that prevents the issue.
One of my colleagues found this issue: Required class was missing org.sonarsource.scanner.maven:sonar-maven-plugin:3.11.0.3922 which suggested to disable plugins. We only had one ( AEM-Rules-for-SonarQube) and disabled it, it looks like that resolved the problems for us.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.