Skip to content

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

Merged
bernardladenthin merged 1 commit into
mainfrom
claude/srcmorph-redirect-cleanup-zst0zm
Jul 27, 2026
Merged

ci(sonar): declare sonar.organization on the reactor root#163
bernardladenthin merged 1 commit into
mainfrom
claude/srcmorph-redirect-cleanup-zst0zm

Conversation

@bernardladenthin

Copy link
Copy Markdown
Owner

Summary

  • Follow-up to the merged repository-rename PR Update repository references from llamacpp-ai-index-maven-plugin to srcmorph #162. After the SonarCloud project key was renamed to bernardladenthin_srcmorph, the analysis job fails client-side with: You must define the following mandatory properties for 'bernardladenthin_srcmorph': sonar.organization.
  • The scanner runs at the reactor root (srcmorph-parent), where sonar.organization was never declared — only the three child modules had it, and child properties are not visible to a parent POM. This was latent until the fresh key tripped SonarCloud's mandatory-property check (the old key was already org-bound server-side).
  • Declares sonar.organization=bernardladenthin in the root <properties>. The projectKey stays a -D argument in .github/workflows/sonarqube.yml.

Test plan

  • Affected unit / integration tests pass locally (no code touched; pom.xml is well-formed)
  • CI is green on this branch (SonarCloud Build and analyze should now pass and populate bernardladenthin_srcmorph)
  • Docs / CHANGELOG updated where applicable (n/a — CI-config only)

Related issues / PRs

Refs #162 (repository rename). Fixes the SonarCloud analysis regression introduced by the project-key rename in that PR.

Checklist

  • I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
  • My commits follow Conventional Commits
  • No security-sensitive changes (if there are, I have notified the maintainer privately per SECURITY.md)

🤖 Generated with Claude Code

https://claude.ai/code/session_01G8uREwBujkenxH1CgTaEGY


Generated by Claude Code

The SonarCloud scanner runs at the reactor root (srcmorph-parent), where
`sonar.organization` was never defined — only the three child modules
declared it, and child properties are not visible to the parent POM. This
was latent: the previous project key was already org-bound server-side, so
the client-side mandatory-property check passed. After the project-key
rename to `bernardladenthin_srcmorph`, the freshly-keyed project trips the
check and the analysis fails with:

  You must define the following mandatory properties for
  'bernardladenthin_srcmorph': sonar.organization

Declare `sonar.organization=bernardladenthin` in the root <properties> so
the reactor-root analysis has it. projectKey stays a workflow -D argument.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G8uREwBujkenxH1CgTaEGY
@bernardladenthin
bernardladenthin merged commit 20b27d8 into main Jul 27, 2026
7 of 12 checks passed
@bernardladenthin
bernardladenthin deleted the claude/srcmorph-redirect-cleanup-zst0zm branch July 27, 2026 19:30
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants