Facing jdk version incompatibility issue in sonar cloud

SonarQube Cloud
1

My project uses jdk1.8

But the sonar cloud uses jdk1.11

How I can build my project from azure pipeline using jdk 1.8

How I can analyze my code using sonarcloud, which uses jdk11

Getting incompatibility error when the pipeline is run

2

Take a look at the documentation on Scanner Environment.

3

My project source code is built using jdk1.8 But the sonar cloud uses jdk1.17 uses for sonar analysis

### 1 The below is the snippet in the azure pipeline:

- task: Maven@4       
  inputs:       
    mavenPomFile: 'pom.xml'
    mavenOptions: '-Xmx3072m'
    javaHomeOption: 'JDKVersion'
    jdkVersionOption: '1.11'
    jdkArchitectureOption: 'x64'
    mavenVersionOption: 'Path'
    mavenDirectory: '/opt/mavenforazure/apache-maven-3.9.3'
    sonarQubeRunAnalysis: true 

    goals: 'clean verify'
    options: '-s=settings.xml -Dsonar.java.jdkHome=/opt/java17/openlogic-openjdk-17.0.9+9-linux-x64

2 The below is the snippet in pom.xml:

org.apache.maven.plugins maven-compiler-plugin 3.8.1 true true 8 1.8 11

3 After the maven task getting the error:

Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.10.0.2594:sonar (default-cli) on project ice-parent:
2024-01-25T13:52:47.2539293Z [ERROR]
2024-01-25T13:52:47.2539462Z [ERROR] The version of Java (11.0.2) used to run this analysis is deprecated, and SonarCloud no longer supports it. Please upgrade to Java 17 or later.
2024-01-25T13:52:47.2539996Z [ERROR] As a temporary measure, you can set the property ‘sonar.scanner.force-deprecated-java-version’ to ‘true’ to continue using Java 11.0.2
2024-01-25T13:52:47.2540246Z [ERROR] This workaround will only be effective until January 28, 2024. After this date, all scans using the deprecated Java 11 will fail.

What are the other configurations should be added to make the sonarcloud task run successfully, Can the support team provide the details on this, Thanks

4

You’lll need to move mvn sonar:sonar to a task after you’ve switched to Java 17.

It would probably be easiest to have two tasks – one with sonarQubeRunAnalysis: false, and then another one with sonarQubeRunAnalysis: true (without clean verify goals) and the JDK set to 17.

5

Hi Colin,
Thanks for the update.

I have tried by having two tasks as mentioned by you.

The first task gets completed success,

The second task fails, it could not find the classes generated from the first step,
Whether the second task need the classes of first task or the sonarQubeRunAnalysis: true takes care of that.

Have attached the snippet of task 1 and task2 for your reference,

- task: SonarCloudPrepare@1
  inputs:
    SonarCloud: 'sonarcloudServiceConnectionInAzure'
    organization: 'orgNAme'
    scannerMode: 'Other'

- task: Maven@4       
  inputs:       
    mavenPomFile: 'pom.xml'
    mavenOptions: '-Xmx3072m'
    javaHomeOption: 'JDKVersion'
    jdkVersionOption: '1.8'
    jdkArchitectureOption: 'x64'
    mavenVersionOption: 'Path'
    mavenDirectory: '/opt/mavenforazure/apache-maven-3.9.3'
    mavenSetM2Home: true        
    codeCoverageToolOption: 'JaCoCo'
    publishJUnitResults: true
    testResultsFiles: '**/surefire-reports/TEST-*.xml'
    effectivePomSkip: false
    sonarQubeRunAnalysis: false
    isJacocoCoverageReportXML: true
    sqMavenPluginVersionChoice: 'latest'
    goals: 'clean install'
    options: '-s=settings.xml 


- task: Maven@4       
  inputs:       
    mavenPomFile: 'pom_sonar.xml'
    mavenOptions: '-Xmx3072m'
    javaHomeOption: 'JDKVersion'
    jdkVersionOption: '1.17'
    jdkArchitectureOption: 'x64'
    mavenVersionOption: 'Path'
    mavenDirectory: '/opt/mavenforazure/apache-maven-3.9.3'
    mavenSetM2Home: true        
    codeCoverageToolOption: 'JaCoCo'
    publishJUnitResults: true
    testResultsFiles: '**/surefire-reports/TEST-*.xml'
    effectivePomSkip: false
    sonarQubeRunAnalysis: true
    isJacocoCoverageReportXML: true
    #sqMavenPluginVersionChoice: 'latest' sonar.exclusions=**/*.java 
    goals: 'sonar:sonar'
    options: ' -s=settings.xml - 
    Dsonar.java.binaries=$(System.DefaultWorkingDirectory)/**/classes

java17 path(export JAVA_HOME_17_X64=/opt/java17/openlogic-openjdk-17.0.9+9-linux-x64)

getting the below error:
The process ‘/opt/mavenforazure/apache-maven-3.9.3/bin/mvn’ failed with exit code 1
2024-01-29T15:07:12.9282265Z Could not retrieve code analysis results - Maven run failed.
If you got any clue for the fix let me know , Thanks

6

I suggest removing this, as it should be automatically set.

If that doesn’t work – attach the full logs from the last step where it fails.

7

Hi Colin,
Thanks for your support and update.

I tried with Dsonar.java.binaries=$(System.DefaultWorkingDirectory)
(where the .class files will be located),
and the sonar analysis run successfully

when I tried without Dsonar.java.binaries during yesterday’s attempt it throws error could not find class files, anyhow will try again and check.

Thanks,
Bascaran