So if I understand correctly the analyzer runs JDT from eclipse and therefore you need that to support Java 15. Is the issue running JDT on Java 15 vs. running JDT on java 11 but JDT supporting Java 15 syntax? I am running Java gradle on Java 15 JVM.
In my case the gradle build is not failing so I assume I am getting partial results in sonar cloud.
Is there a way to find how much of the analysis is not being done?
If I run the analyzer on Java 11 will it work with Java 15 sources and compiled bytecode?
To be honest, I have no clue how our scanners behave running on Java 15 (only Java 11 is officially supported, but we try and keep compatibility with newer versions of Java). There have been no other reports of issues using the scanner with Java 15, and the log message you showed would be one it throws specifically during Java analysis (not running analysis overaell)
Java 15-specific syntax is definitely not yet supported.
Adding --debug to your Gradle command will show a lot more logs, and may give you some confidence that it’s just happening on a single file vs. many.
In the future, yes – as far as I’m aware you should be able to analyze Java 15 code (run the scanner) with Java 11.
I don’t know! I’ll ping the right person internally, and maybe they can take a look at the docs.
Thanks for ticket to add toolchains it really makes things simpler for users like me. I have reviewed my CI pipeline logs and it seems that I am getting the warning even before I upgraded to Java 15, even when running on Java 11.