SLCORE-2226, SLCORE-2227 Migrate to Java 21

[damien-urruty-sonarsource]

No description provided.

[hashicorp-vault-sonar-prod]

SLCORE-2226
SLCORE-2227

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[sonar-review-alpha]

Summary

Migrates SonarLint backend and CLI to Java 21 while preserving Java 11 compatibility for the client SDK. The change introduces separate parent POMs for backend and client modules, allowing backend to target Java 21 (taking advantage of newer dependencies that now require it) while keeping the client on Java 11 for OSGi/Eclipse compatibility. The Sloop CLI distribution bundle is updated to JDK 21, and CI/CD workflows are streamlined with a cleaner approach to orchestrator Java version handling.

What reviewers should know

Start by reviewing the parent POM changes: pom.xml now sets maven.compiler.release to 21, and new backend/pom.xml and client/pom.xml establish the module hierarchy. Note that client/pom.xml explicitly overrides to Java 11 with a clarifying comment. Then check the backend/* modules to verify their parent references changed from sonarlint-core-parent to sonarlint-backend-parent. The CLI changes are in backend/cli/pom.xml where JRE downloads were bumped from 17 to 21 (verify the new sha256 hashes). Finally, review .github/workflows/build.yml - the matrix no longer has a generic java property; only SQLts99 now needs Java 17 via customOrchestratorJavaVersion for compatibility testing, which the workflow sets as ORCHESTRATOR_JAVA_HOME instead of the default.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonar-review-alpha]

Conclusion: Clean, well-executed migration. The parent-POM split into sonarlint-backend-parent (Java 21) and sonarlint-client-parent (Java 11) is the right structural move and the compiler overrides are consistently applied. JRE hashes for the same binaries (windows_x64, linux_x64) are identical between backend/cli/pom.xml and medium-tests/pom.xml, which is reassuring. The ORCHESTRATOR_JAVA_HOME approach in CI correctly keeps the build on Java 21 while giving Orchestrator a Java 17 home only for the SQLts99 matrix entry.

🗣️ Give feedback

[eray-felek-sonarsource]

LGTM. Let's merge this after we make sure all the consumer IDEs are green