From 4b51969a45dd39490e04d58e2482608755004d44 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Mon, 27 Jul 2026 19:27:21 +0000
Subject: [PATCH] ci(sonar): declare sonar.organization on the reactor root
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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
---
 pom.xml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/pom.xml b/pom.xml
index 9ebb28f..6618492 100644
--- a/pom.xml
+++ b/pom.xml
@@ -60,6 +60,13 @@ SPDX-License-Identifier: Apache-2.0
             at this level. srcmorph-cli/pom.xml does not redeclare it.
         -->
         <jackson.version>2.22.1</jackson.version>
+        <!--
+            SonarCloud requires sonar.organization on the project the scanner executes, which is
+            this reactor root (srcmorph-parent) — child-module properties are not visible to the
+            parent POM. The child modules also declare it for standalone/module-scoped runs; the
+            projectKey stays a workflow -D argument (see .github/workflows/sonarqube.yml).
+        -->
+        <sonar.organization>bernardladenthin</sonar.organization>
     </properties>
 
     <!--