ci(sonar): declare sonar.organization on the reactor root - #164
Merged
bernardladenthin merged 1 commit intoJul 27, 2026
Merged
Conversation
The SonarCloud scan runs at the reactor root (.github/workflows/sonarqube.yml calls 'mvn ... sonar:sonar' with no -f, so the analyzed project is the srcmorph-parent POM). sonar.organization was declared only in the child module POMs, and a parent POM never sees its children's <properties>, so the root scan failed with: You must define the following mandatory properties for '<projectKey>': sonar.organization Declare sonar.organization=bernardladenthin on the reactor root so the scanner sees it. Left in the child modules too (harmless). projectKey is unchanged (stays the -D argument in the workflow). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MeheJtyQwUzJGLcYpyWURD
bernardladenthin
had a problem deploying
to
startgate
July 27, 2026 19:38 — with 
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
July 27, 2026 19:38 — with
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
maven-central
July 27, 2026 19:38 — with
GitHub Actions
Failure
GitHub Actions
Failure
|
bernardladenthin
deleted the
claude/dependency-plugin-updates-audit-lcubyh
branch
July 27, 2026 19:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
You must define the following mandatory properties for '<projectKey>': sonar.organization.sonar.organizationwas declared only in the child module POMs (srcmorph,srcmorph-cli,srcmorph-maven-plugin), but the scan runs at the reactor root —.github/workflows/sonarqube.ymlcallsmvn ... sonar:sonarwith no-f, so the analyzed project is thesrcmorph-parentrootpom.xml. A parent POM never sees its children's<properties>, so the root scan had nosonar.organization.<sonar.organization>bernardladenthin</sonar.organization>in the reactor-rootpom.xml<properties>(with an explanatory comment). Left in the child modules too (harmless).projectKeyis unchanged — it stays the-Dsonar.projectKey=bernardladenthin_llamacpp-ai-index-maven-pluginargument in the workflow.Scanner-root POM changed:
pom.xml(reactor root,net.ladenthin:srcmorph-parent,packaging=pom).Test plan
pom.xmlverified well-formed (mvn -N -o validate→ BUILD SUCCESS; XML parse check)sonar.organization)Related issues / PRs
Checklist
Generated by Claude Code