Skip to content

ci(sonar): declare sonar.organization on the reactor root #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bernardladenthin merged 1 commit into from
Jul 27, 2026
Merged

ci(sonar): declare sonar.organization on the reactor root #164

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,16 @@ SPDX-License-Identifier: Apache-2.0
</distributionManagement>

<properties>
<!--
SonarCloud requires sonar.organization on the project the scanner actually analyzes.
The SonarCloud scan runs at THIS reactor root (.github/workflows/sonarqube.yml calls
`mvn ... sonar:sonar` with no -f, so the analyzed project is this parent POM), and a
parent POM never sees its children's <properties>. Declaring it only in the child
modules therefore left the root scan without it, failing with
"You must define the following mandatory properties for '<projectKey>': sonar.organization".
Kept in the child modules too (harmless) so a per-module scan would also carry it.
-->
<sonar.organization>bernardladenthin</sonar.organization>
<!--
Defined here (not only in srcmorph-cli/pom.xml) because this parent's own
<dependencyManagement> below references it: child properties are never visible to a
Expand Down
Loading