which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
Upgraded sonarqube server version from 9.9 to 10.7 (DE)
Scanner version 5.0 ( using java 17 on scanner )
how is SonarQube deployed: zip, Docker, Helm
Zip - running on EC2 instance
what are you trying to achieve
testing the sonarqube version upgrade from 9.9 to 10.7
what have you tried so far to achieve this
Upgraded the version successfully and trying to test different version of java repo scanning (java11/java17/java21 and java8/java1.8)
After upgrading sonarqube server version to 10.7 and upgrading sonar scanner environment to use java version 17 – the sonar scan of java repositories which are on JAVA 11 version are failing… could you please confirm if the newer version of sonarqube server(10.7) and scanner environment (with java version 17) supports scanning of java repos which are on java version 11.
Error:
2024-11-13 16:19:17.092 [main] ERROR org.apache.maven.cli.MavenCli - Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar (default-cli) on project dynamo-beam-framework: Execution default-cli of goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar failed: An API incompatibility was encountered while executing org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar: java.lang.UnsupportedClassVersionError: org/sonar/batch/bootstrapper/EnvironmentInformation has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0
At least the minimal version of Java supported by your SonarQube server is in use
so it is possible to scan to java code with version 8/11/17/21 with sonarqube version 10.7 and scanner version 5.0 (given, scanner env using java 17) with updated sonar-maven plugin - Please confirm.
you will use either Sonar CLI Scanner (the latest version is 6.2.1) or the
sonar-maven plugin (latest version is 5.0.0.4389).
While using an older version of the CLI scanner or the sonar-maven plugin might still work,
i recommend to use the latest version especially if you’re running Sonarqube 10.7.0 LATEST.
you will use either Sonar CLI Scanner (the latest version is 6.2.1) or the
sonar-maven plugin (latest version is 5.0.0.4389).
Upgrading the sonar scanner cli to latest version 6.2.1 is still giving same error.
we have some challenges/blockers to upgrade sonar-maven plugin to latest.
could you please confirm if we we can chose any other version of sonarqube server other than 10.7 that supports scanning of java 21 also compatible with java 11…21 without having to upgrade sonar-maven plugin…
What are the blockers ?
Anyway, if the Sonarqube analysis (the goal sonar:sonar) within your Maven build - also with org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184 - runs with Java >= 17 all is fine.
We use two different mvn calls for legacy projects, the first does the build for the project on Java 8/11 … and the second call runs with Java 17 for the Sonarqube analysis = mvn sonar:sonar
we were able to procure the latest version of the sonar-maven plugin.
updated the sonar-maven plugin for the repositories that were still running on Java 11 (JDK 11).
Everything seems fine at the moment. Thank you so much for your guidance. Please feel free to close this thread.