From 5e373973b4d9f55788164c3ae3254efbbbfd722c Mon Sep 17 00:00:00 2001
From: Vincent Paturet <vincent.paturet@entur.org>
Date: Mon, 7 Sep 2026 14:40:49 +0200
Subject: [PATCH] Remove stale sonar-maven-plugin version override in sonar
 profile

The `sonar` profile pinned sonar-maven-plugin to 3.9.1.2184, overriding
the 5.5.0.6356 declared in the top-level properties. Since the CI Sonar
step activates `-Psonar`, the ancient scanner was the one actually
running, and it fails on Java 17 now that SonarQube Cloud requires
Java 21 or newer:

    Java 17 is not supported. Please upgrade to Java 21 or newer, or use
    JRE auto-provisioning to keep this requirement always up to date.

Scanner 5.5 runs on Java 17 and auto-provisions a JRE for the analysis
engine, so the workflow can keep using `setup-java: 17`.
---
 pom.xml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index b0c7bb2..9f13eec 100644
--- a/pom.xml
+++ b/pom.xml
@@ -681,7 +681,6 @@
 
             <properties>
                 <jdk.version>11</jdk.version>
-                <sonar-maven-plugin.version>3.9.1.2184</sonar-maven-plugin.version>
             </properties>
 
             <build>