Open sseide opened 3 years ago
I'm clearly behind on issues on this repo.
I looked at the official Sonar Scanner docker image and it appears they're using JDK 11 as you point out. I honestly don't do much Java work these days, so I'm assuming anyone using this image for Java scanning won't be losing anything by moving to Java 11? Given how long the 4.x scanner image has been out there, I'm surprised no one's mentioned this before. I'm a little concerned by rolling back the image's base image a major Java version. Is there an example project where I can see this behavior and reproduce the issue? Any other comments on this?
yes - jdk 11 as the current long-term release should be fine for everyone today.
last month java17 was release as the next LTS release (after 11), but this one will definitly break build for lots of packages i think due to the move to java modules in between. A lot of libraries need to adopt to this i think...
As a side note - one issue we had with sonarqubes own image - the missing curl and/or wget will be fixed by them. The finally accepted the need for an command line tool that can handle https correctly... Due to this we are able to use the official image too by now.
Thanks for this image - we are using the older "alpine" images up to now and were trying to switch to the newer 4-version.
Tried latest version of image "4" but it fails with error message because its using a "ea" (early adoptor) version of Java12 not allowed for sonar-qube scanner. And Java12 is EOL for some time now, therefore not getting any updates since two years.
Please switch back to Java 11 LTS (supported by sonar-scanner). Current Java 16 is no LTS release either (will be out of support in 6 months and next LTS version 17 is not release by now.
reference at sonarsource about !"ea" releases: https://community.sonarsource.com/t/java-12-support/11864
Thanks, Stefan Seide
Execption running sonar-scanner on latest imge with tag "4"