Yes, it used to work as described in Exit code list of sonar-scanner command - #4 by Colin
However, the behaviour has changed after we migrated to 2025.2.
Looking at sonar/scan source code, it seems that JRE provisioning is based on Sonar version - only versions equal or above 10.6 are accepted:
sonar-scanner-npm/src/java.ts at master · SonarSource/sonar-scanner-npm · GitHub
Have tried setting sonar.scanner.skipJreProvisioning=true without any luck. I believe this attribute is checked later, after Sonar CLI option is already discarded:
The scan fails because Java is not found in the path, but it would still try to use Sonar Engine instead of CLI.
We are on sonar/scan v 4.3.0 btw. It’s the latest version.