DO NOT MERGE S6541: reduce noise by dividing found issues count by 15 instead of 10

[asya-vorobeva]

---

Summary by Gitar

• Bug fixes and logic changes:
  • Updated S6541 logic to divide the found issues count by 15 instead of 10 to reduce noise.
• Project configuration:
  • Added sonar-java as a required dependency for Kotlin projects in the build configuration.

_{This will update automatically on new commits.}

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[gitar-bot]

CI failed: Integration test failures occurred in the `JavaRulingTest` suite across multiple platforms, specifically in the `eclipse_jetty_incremental` test case, due to the logic change in issue counting.

Overview

Two separate CI environments reported integration test failures in JavaRulingTest.eclipse_jetty_incremental following the proposed changes to the S6541 issue counting logic. The tests failed because the actual number of reported issues no longer matches the hardcoded expectations in the test suite.

Failures

Integration Test Regression in JavaRulingTest (confidence: high)

• Type: test
• Affected jobs: Ruling QA, 84083705716
• Related to change: yes
• Root cause: The logic modification for S6541 (changing the divisor from 10 to 15) has altered the number of issues reported during incremental analysis. The test eclipse_jetty_incremental expects a specific count that is now outdated.
• Suggested fix: Review the eclipse_jetty_incremental test case in org.sonar.java.it.JavaRulingTest. If the new reporting behavior is intentional, update the test's expected output resources to reflect the new counts. If the discrepancy is unintended, verify the arithmetic logic in the S6541 implementation.

Summary

• Change-related failures: 2 test failures confirmed, directly caused by the modification of the issue counting algorithm.
• Infrastructure/flaky failures: 0 (minor Develocity connectivity warnings observed but did not block the core test execution).
• Recommended action: The developer should update the affected integration test expectations to match the new behavior introduced by the pull request.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}