Fix remote debugging of Ruling tests

[leveretka]

Part of

[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
No data about Duplication

See analysis details on SonarQube

[sonarqubecloud]

🤖 Pull Request summary

Updates debug environment variable name in SlangRulingTest.

• Changed SONAR_SCANNER_DEBUG_OPTS to SONAR_SCANNER_JAVA_OPTS for debug configuration

Review focus: Verify this aligns with SonarScanner's expected environment variable naming.

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonar-review-alpha]

Summary

Changes the environment variable used to pass debug options to the Sonar Scanner during ruling test execution. The fix switches from SONAR_SCANNER_DEBUG_OPTS to SONAR_SCANNER_JAVA_OPTS, which is the correct variable name recognized by the scanner for passing JVM debug arguments when remote debugging is enabled.

What reviewers should know

Single-line change in its/ruling/src/test/java/org/sonarsource/slang/SlangRulingTest.java:254

The change is in the debug port configuration block (lines 251-256) that runs when sonar.rulingDebugPort system property is set. The fix ensures debug options are properly forwarded to the scanner's JVM when developers enable remote debugging.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[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
No data about Duplication

See analysis details on SonarQube