Skip to content

Commit 017b21f

Browse files
dfa1claude
andcommitted
chore(performance): exclude module from SonarCloud analysis
The performance module is diagnostic CLI tooling (JMH benchmarks + ad-hoc taxi inspectors), not shipped library code. By-design uses of System.out/err, java.io.tmpdir, and main(String[] args) dominate the Sonar findings (120 issues, mostly S106/S5443/S1172 false-positives for this category) with no library-quality signal. Reader/writer/core/cli stay under full analysis. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
1 parent 1e5816a commit 017b21f

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

performance/pom.xml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,12 @@
1515
<properties>
1616
<maven.deploy.skip>true</maven.deploy.skip>
1717
<skipShade>true</skipShade>
18+
<!-- This module is diagnostic CLI tooling (JMH benchmarks + ad-hoc taxi-data inspectors),
19+
not shipped library code. By-design uses of {@code System.out}, {@code System.err},
20+
{@code java.io.tmpdir}, and {@code main(String[] args)} dominate the Sonar findings
21+
and have no library-quality signal. Excluded from analysis to keep the dashboard
22+
focused on library modules. -->
23+
<sonar.skip>true</sonar.skip>
1824
</properties>
1925

2026
<dependencies>

0 commit comments

Comments
 (0)