Use correct property for multimodule jacoco report

[andres-garciasolares-sonarsource]

Docs say to use sonar.coverage.jacoco.aggregateXmlReportPaths, and some side effects seem to happen when you use the wrong prop.

[gitar-bot]

CI failed: The 'verify-sca' check failed because the SCA scanner could not locate the SonarQube project for this repository, resulting in a timeout.

Overview

The verify-sca CI job failed across two parallel runs because the automated scanning tool could not find a corresponding project in SonarQube. This indicates a mismatch between the repository's inferred project key and the actual project key registered in the SonarQube platform.

Failures

SCA Project Discovery Timeout (confidence: high)

• Type: test
• Affected jobs: 87350935591, 87352132019
• Related to change: yes
• Root cause: The check-sca action is defaulting to a project key (SonarSource_sonar-scanning-examples) that does not match the project name or key recognized by the SonarQube instance.
• Suggested fix: Explicitly define the project key in your configuration. Check .github/repo-metadata.yaml and set the check-sca.project-key property to match the correct identifier used in SonarQube. Additionally, ensure that a scan has been successfully triggered for this project previously.

Summary

• Change-related failures: 1 (SCA verification failure blocking the CI pipeline)
• Infrastructure/flaky failures: 0
• Recommended action: Update the repository's metadata to explicitly specify the correct SonarQube project key to resolve the lookup failure.

Code Review ✅ Approved 1 resolved / 1 findings

Updates the Maven documentation to use the sonar.coverage.jacoco.aggregateXmlReportPaths property, resolving the previously incorrect usage of xmlReportPaths for multi-module projects.

✅ 1 resolved

✅ Quality: README still documents non-aggregate xmlReportPaths property

📄 sonar-scanner-maven/maven-multimodule/README.md:85 📄 sonar-scanner-maven/maven-multimodule/pom.xml:24
The pom.xml now correctly uses sonar.coverage.jacoco.aggregateXmlReportPaths, but README.md line 85 still instructs users to set sonar.coverage.jacoco.xmlReportPaths in the top-level pom.xml (and line 92's CLI example uses the same property, plus a pre-existing sonar..coverage double-dot typo). Update the README snippet to use aggregateXmlReportPaths so the docs match the corrected pom and avoid the same side effects this PR is fixing.

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 the behavior for this request:

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

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