CLP-212: Migrate scanner test fixtures

[vdiez]

Summary

• replace the SonarQube implementation artifact with scanner-engine 13.4.1 test fixtures across affected modules
• migrate moved scanner implementation imports and use TestSonarRuntime
• remove unused implementation and Plugin API test-fixture dependencies from modules that need neither
• declare JUnit 4 directly where the removed artifact previously supplied it transitively

Dependency changes

Before: analyzer tests relied on org.sonarsource.sonarqube:sonar-plugin-api-impl, including for scanner implementation types and transitive scanner helpers.

After: affected modules directly declare plugin-api-scanner-impl and sensor-test-fixtures; java-frontend also directly declares sonar-scanner-extension-framework for PropertyDefinitions. All scanner artifacts use 13.4.1.4007. The four modules whose forbidden-API checks inspect RunWith now declare JUnit 4 directly. The resolved Maven graph contains no sonar-plugin-api-impl.

sonar-plugin-api-test-fixtures is retained only in modules that still use its logging helpers.

Validation

• affected reactor test compilation on Java 26
• Maven dependency-tree check for org.sonarsource.sonarqube:sonar-plugin-api-impl (no matches)
• git diff --check

Running the complete local test suite additionally requires the repository's prebuilt java-checks-test-sources/*/target/test-classpath.txt inputs; affected test compilation is green without them.

[hashicorp-vault-sonar-prod]

CLP-212

[aurelien-coet-sonarsource]

LGTM, just a small question.

[aurelien-coet-sonarsource]

Why is this now an explicit dependency ?

[vdiez]

JUnit 4 was already on this module's test classpath transitively through sonar-plugin-api-impl. Removing that artifact made the forbiddenapis:testCheck execution (forbid-junit4) fail because its signature file references org.junit.runner.RunWith and that class could no longer be resolved. This declaration makes that existing build-time requirement explicit; the module's tests remain on JUnit 5.

[vdiez]

More precisely, no JUnit test was failing. The failure was the Test Analyze CI job, in the external-reports Maven execution:

Failed to execute goal de.thetaphi:forbiddenapis:3.10:testCheck (forbid-junit4) on project external-reports: Parsing signatures failed: Class 'org.junit.runner.RunWith' not found on classpath while parsing signature: org.junit.runner.RunWith

The referenced signature is forbid_junit4.txt:9. The explicit dependency is only there so this check can resolve the class it forbids.

[vdiez]

added a comment in the pom directly so we don't lose track of why this is needed

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
2 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

[gitar-bot]

Code Review ✅ Approved

Migrates scanner test fixtures to version 13.4.1 and decouples dependencies from the SonarQube implementation artifact. No issues found.

Options

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

Comment with these commands to change the behavior for this request:

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

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