From b4dd0eb21cafdbd4108a4ef505209690eba60f65 Mon Sep 17 00:00:00 2001 From: Travis Date: Tue, 15 Sep 2026 16:44:57 +0000 Subject: [PATCH] Build: add a project-specific SonarQube scan Configures the org.sonarqube plugin so each spring-* sub-module is analyzed as its own SonarQube project keyed org.springframework:, rather than as a single aggregated scan of the whole build. Each module's configuration lives in its own build file so it can be reviewed and merged independently. Server URL and token are read from the SONAR_HOST_URL and SONAR_TOKEN environment variables rather than being hardcoded. --- spring-messaging/spring-messaging.gradle | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/spring-messaging/spring-messaging.gradle b/spring-messaging/spring-messaging.gradle index a611cf669825..863a9f8c25b0 100644 --- a/spring-messaging/spring-messaging.gradle +++ b/spring-messaging/spring-messaging.gradle @@ -1,3 +1,7 @@ +plugins { + id 'org.sonarqube' version '7.4.0.8496' +} + description = "Spring Messaging" apply plugin: "kotlin" @@ -44,3 +48,13 @@ dependencies { testRuntimeOnly("jakarta.json:jakarta.json-api") testRuntimeOnly("org.eclipse:yasson") } + +// This module is analyzed as its own SonarQube project. +sonar { + properties { + property 'sonar.projectKey', 'org.springframework:spring-messaging' + property 'sonar.projectName', 'Spring Messaging' + property 'sonar.projectVersion', project.version + property 'sonar.sourceEncoding', 'UTF-8' + } +}