Error Prone Plugin Not Applied and Build Passes Despite Errors #18470
Summary
The Error Prone plugin is not being applied correctly, and even after promoting all disabled checks and warnings to errors, the build still passes. This issue surfaced after splitting tools in the CI configuration.
Details
After splitting the tools in our CI setup, we observed behavior that indicates Error Prone is either not executed or not enforced as expected. Specifically:
- The Error Prone plugin does not appear to be applied.
- When all disabled checks and warnings are promoted to errors, the build still succeeds.
- This raises concerns about whether static analysis tools are properly configured and enforced in CI.
Related Links
Expected Behavior
- The Error Prone plugin should be applied consistently in both local and CI builds.
- When warnings and disabled checks are promoted to errors, the build should fail.
- CI should reliably enforce Error Prone violations and fail the build when issues are present.
Current Behavior
- Error Prone plugin is not applied.
- Promoting all disabled checks and warnings to errors does not fail the build.
- CI reports success even when Error Prone violations should cause a failure.
Impact
- Static analysis rules are not enforced as intended.
- Developers may get a false sense of build correctness.
- Code quality issues may be merged undetected.
Notes
This likely indicates a configuration issue introduced during the CI tool split. We need to verify:
- Whether the Error Prone plugin is correctly applied in all relevant modules.
- Whether CI is invoking the same build configuration as local runs.
- If Error Prone is being skipped, disabled, or downgraded in CI execution.
PS:
Happy New Year 🎉
Let’s start the new one as the previous ended — well — with great improvements driven by community effort and time.
Error Prone Plugin Not Applied and Build Passes Despite Errors #18470
Summary
The Error Prone plugin is not being applied correctly, and even after promoting all disabled checks and warnings to errors, the build still passes. This issue surfaced after splitting tools in the CI configuration.
Details
After splitting the tools in our CI setup, we observed behavior that indicates Error Prone is either not executed or not enforced as expected. Specifically:
Related Links
spotbugsandpmdconfig withrewrite#18454 #18479 #18440StaticImportis something thats not complain with checkstyle currently, therefore this seems to be kind of out of sync as well.Expected Behavior
Current Behavior
Impact
Notes
This likely indicates a configuration issue introduced during the CI tool split. We need to verify:
PS:
Happy New Year 🎉
Let’s start the new one as the previous ended — well — with great improvements driven by community effort and time.