Remove unused SpotBugs suppressions from dd-smoke-tests#11831
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
|
/merge -f --reason "Removed unused annotations, no need in MQ" |
|
View all feedbacks in Devflow UI.
The expected merge time in
Warning This change was merged without running any pre merge CI checks Reason: Removed unused annotations, no need in MQ |
d3398ea
into
master
What Does This Do
Removes now-dead SpotBugs artifacts from
dd-smoke-tests:@SuppressFBWarningsannotations and theiredu.umd.cs.findbugs.annotations.SuppressFBWarningsimports across the IAST, XSS, APM-tracing-disabled and profiling smoke-test apps.compileOnly 'com.github.spotbugs:spotbugs-annotations'dependency fromapm-tracing-disabled/application/build.gradle.Motivation
SpotBugs is disabled for the entire
:dd-smoke-testssubtree ingradle/spotbugs.gradle:Since the analysis never runs on these fixtures, the
@SuppressFBWarningsannotations and thespotbugs-annotationsdependency are pure dead weight.Additional Notes
com.google.code.findbugs:jsr305is intentionally kept — it provides@Nonnull/@Nullableused by the Spring Boot fixtures, unrelated to SpotBugs analysis.jboss-modulesstill carries anexclude module: 'spotbugs-annotations'on its custom configurations; left as-is since it's a harmless transitive-exclude, not an analysis config.🤖 Generated with Claude Code