We are using SonarQube in a big organization with hundreds of repos, most of them Java 8. We want to write new services in Java 17. But SonarQube is blocking us, because 9.2 supports ONLY Java 11+, while 8.9 supports only 8-15 (I think? But not 17 for sure).
It is not an option to go and update all of the existing repos to Java 11 just for the SQ. Running the build with Java 11 also doesn’t work out of the box, the effort would be comparable to upgrading all the repos.
Running sonar separately in docker might have been an option, but again, it requires us to update all of the projects. Plus, it is very slow for some reason. If we could use this way only for the new projects with Java 17+, that would be fine. But here we need to update all of the old projects.
Running 2 different SQ servers probably requires 2 licenses, right? Also not an option.
So, to reiterate, this artificial requirement to not analyze Java 17 in 8.9 and not analyze java 8 in 9.+ is blocking us. Is there an option to include older scanners into 9.+?