Java 11 is deprecated as a runtime env to scan your projects

Just like said in this post Java 11 is set to deprecate on 1/15/24

“This project was scanned using Java 11 runtime. Starting from Jan 15, 2024, SonarCloud will stop accepting scans that are started with Java 11. We highly recommend moving your configuration to Java 17+.”

Though we’re using SonarCloud. A GitHub App we installed. This is a SaaS tool, configured on your end, why would I need to update anything on my end?

Hi @danielzev,

Analysis uses Java - installed and called in your build environment / CI/CD - to run. So you’ll need to make sure the version of Java it’s using is upgraded to Java 17.

 
HTH,
Ann

1 Like

Are you using the latest version of the sonarsource/sonarcloud-scan (2.0)?

Using 1.0
sonar.projectVersion=1.0

Should I use version 2.0?
sonar.projectVersion=2.0

Hi @Sunil_Bobbala,

Upgrading Java on Bitbucket isn’t really in our scope. What I can say is that this has nothing to do with your sonar.projectVersion value. Instead, this is about the version of Java installed on your build agent and used by your BB job.

 
HTH,
Ann

1 Like

What is the minimum required version for the Gradle plugin, because it’s not in the table above.
We have 3.3, and it seems ok (the warning disappeared once Gradle was running on Java 17).

Which brings me to another question: is it enough if on the PR that changes CI to 17 the warning is not showing any more? (i.e. how to verify that we’ve upgraded correctly?)

Hi,

Welcome to the community!

No warnings means you’re good.

 
HTH,
Ann

4 posts were split to a new topic: Can’t use Java17 using Scanner for NPM

A post was split to a new topic: Question about upgrade to SQ 10.4 and Java versions

A post was split to a new topic: Fail to scan on Azure pipeline: Java11 is deprecated

4 posts were split to a new topic: Can’t scan my project using Java11

A post was split to a new topic: JAVA_HOME_17 var required for ADO task

A post was split to a new topic: Question about Code Coverage related to Java11 to Java17 migration

Hey! We do use Java 17 on our running agent, but we still see a warning. Could you please assist on how we can mitigate this?


Hey there.

Have you reanalyzed the main branch of your project recently?