Skip to content

chore: stop reporting removal warnings for test sources - #25825

Open
totally-not-ai[bot] wants to merge 1 commit into
mainfrom
chore/silence-removal-warnings-in-test-compile
Open

totally-not-ai[bot] wants to merge 1 commit into
mainfrom
chore/silence-removal-warnings-in-test-compile

Conversation

@totally-not-ai

@totally-not-ai totally-not-ai Bot commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Test code calls deprecated-for-removal APIs on purpose, so the compiler's removal warnings there are just noise. This turns those warnings off for test sources only.

What changed

  • Added <testCompilerArgument>-Xlint:-removal</testCompilerArgument> to the shared maven-compiler-plugin configuration in the root pom.xml, so src/test no longer reports removal warnings.
  • src/main is untouched: calling a deprecated-for-removal API in production code still warns, because that is a real finding.

This is a build-only change. No behavior change for users of Flow, and no source changes — it only makes build output quieter. For reference, a build of flow-server, flow-data and flow-html-components printed 309 removal warnings, 186 of them from test sources.

Tests keep calling APIs that are deprecated for removal on purpose, so
the removal lint only adds noise there: of the 309 warnings a build of
flow-server, flow-data and flow-html-components printed, 186 came from
src/test. The lint stays on for src/main, where such a call is a real
finding.
@sonarqubecloud

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown
Contributor

Test Results

 1 455 files  ±0   1 539 suites  ±0   1h 29m 52s ⏱️ +26s
11 939 tests ±0  11 871 ✅ ±0  68 💤 ±0  0 ❌ ±0 
12 257 runs  ±0  12 189 ✅ ±0  68 💤 ±0  0 ❌ ±0 

Results for commit f4e0c18. ± Comparison against base commit 88ceac1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants