This is an automated email from the ASF dual-hosted git repository.

apupier pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 0b2623bc17cdabe82dc52cea13d32d13c1640956
Author: Aurélien Pupier <[email protected]>
AuthorDate: Thu Nov 19 11:00:30 2026 +0100

    CAMEL-27163: Mention sonar-build.yml in the comments of the coverage profile
    
    Address the review: sonar-build.yml also runs the merge and per-module 
report executions.
    
    AI-assisted: IBM Bob 2.2.1 on behalf of Aurélien Pupier (@apupier).
    
    Co-authored-by: IBM Bob 2.2.1
    Signed-off-by: Aurélien Pupier <[email protected]>
---
 parent/pom.xml | 2 +-
 pom.xml        | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/parent/pom.xml b/parent/pom.xml
index 0e4d80b3f185..add281243092 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -4674,7 +4674,7 @@
                             <!-- Generates the coverage report of one module 
from the execution data of all the modules
                                  merged by the "coverage" profile of the root 
pom (some modules are covered by the tests of other modules).
                                  Not bound to the build: run it with "mvn 
-Pcoverage jacoco:report@report-module"
-                                 after the merge of the execution data, see 
the Jenkinsfile. -->
+                                 after the merge of the execution data, see 
the Jenkinsfile and sonar-build.yml. -->
                             <execution>
                                 <id>report-module</id>
                                 <phase>none</phase>
diff --git a/pom.xml b/pom.xml
index 671186739dad..eaad3e68cf4e 100644
--- a/pom.xml
+++ b/pom.xml
@@ -120,7 +120,7 @@
         
<project.build.outputTimestamp>2026-10-15T12:33:02Z</project.build.outputTimestamp>
 
         <sonar.java.source>${jdk.version}</sonar.java.source>
-        <!-- Each module reads its own coverage report, generated by 
"jacoco:report@report-module" (see the Jenkinsfile).
+        <!-- Each module reads its own coverage report, generated by 
"jacoco:report@report-module" (see the Jenkinsfile and sonar-build.yml).
             Pointing every module to the aggregated report instead makes the 
analysis parse that huge report once per module. -->
         
<sonar.coverage.jacoco.xmlReportPaths>${project.build.directory}/site/jacoco/jacoco.xml</sonar.coverage.jacoco.xmlReportPaths>
         <sonar.cpd.exclusions>
@@ -715,8 +715,8 @@
     <profiles>
         <profile>
             <!-- Merges the execution data collected in each module by the 
"coverage" profile of the parent pom, in one file used to
-                 generate the coverage report of each module 
(jacoco:report@report-module, see the Jenkinsfile): some modules are
-                 covered by the tests of other modules.
+                 generate the coverage report of each module 
(jacoco:report@report-module, see the Jenkinsfile and sonar-build.yml):
+                 some modules are covered by the tests of other modules.
                  Not bound to the build, run it once the modules are built 
with:
                  mvn -N -Pcoverage 
org.jacoco:jacoco-maven-plugin:merge@merge-all -->
             <id>coverage</id>

Reply via email to