Projects having Zero Code Coverage when scanned along with Java 11 Configs

[narayananpalanimarco (Narayanan Palani)]

@Colin

Your scans probably stopped being submitted to SonarCloud after the requirement changed from Java 11 to Java 17. This can probably be fixed just by making sure Java 11 is available in your CI environment, and switching to that distribution before running analysis. You can see some examples here.

Thank you, Colin! CI got Java 11 and couple of microservices are scanned by keeping sonar properties such as,

sonar.java.source=11

But the status errored in sonar as:
This project was scanned using Java 11 runtime. Starting from 15 Jan 2024, SonarCloud will stop accepting scans that are started with Java 11. We highly recommend moving your configuration to Java 17+.

If the Java 11 made available within Sonar to scan part of CI, it should scan the Code Coverage to produce right figure to dashboard based on expected scan coverage. But the code coverage showing ZERO which is not expected here: