From 5e74257633b3e1340ecb64073034bba8c9ffa7a3 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Mon, 27 Jul 2026 19:38:01 +0000
Subject: [PATCH] ci(sonar): declare sonar.organization on the reactor root

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

diff --git a/pom.xml b/pom.xml
index 1f10989..9b29e4c 100644
--- a/pom.xml
+++ b/pom.xml
@@ -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