How to solve the problem of inconsistent JDK versions between sonarQube local scan and Maven project

[lcrazyl (swifts Lee)]

Must-share information (formatted with Markdown):

• which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
  9.9
• how is SonarQube deployed: zip, Docker, Helm
  zip
• what are you trying to achieve
  Thank you very much for your answer. I have successfully upgraded to version 9.9, but the minimum version of JDK required by 9.9 is 11, and my project is built using JDK1.8

How to solve the problem of inconsistent JDK versions between sonarQube local scan and Maven project build?

In addition, why does the command executed by the local scan of sonarQube9.9 version maven project is mvn clean verify?

• what have you tried so far to achieve this

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

[Colin]

It looks like you asked this question (and got an answer) over here:

Java rule false positive

I think the documentation on Scanner Environment should help you. Maven / Gradle If your whole Maven or Gradle build doesn’t run on Java 11 or 17, we suggest first to try to base the whole build on one of those two versions of Java. If it’s not compatible, then you can override the JAVA_HOME environment variable just before the analysis step, as shown here: # Maven build mvn verify ... export JAVA_HOME=/path/to/java-11-or-17 mvn sonar:sonar ...

I’ll close this thread as a duplicate.