Bump errorprone to 2.38.0 #95
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR
Error-prone 2.38.0 has ABI breaks since 2.31.0. Internally, open source libraries that depend on
error-prone-annotationsare bumping up error-prone to 2.38.0, and these errors are manifesting. We should be on latest.We upgraded baseline here: palantir/gradle-baseline#3121
After this PR
==COMMIT_MSG==
Bump errorprone to 2.38.0
==COMMIT_MSG==
Most of the test changes are just tidy up to get rid of the
System.outs that errorprone now complains about.Possible downsides?
This repo has is stuck on a really old version of baseline, because the moment baseline started applying suppressible-error-prone, there is this weird self-referential error as Gradle tries to replace the
suppressible-error-pronemodule with the local project (and requiring it's own jar before the :To work around this, I've not upgraded the gradle plugin but have upgraded the
baseline-error-pronejar that contains the error prone checks. We need this upgraded as these baseline checks were broken by upgrading error-prone.I'm working on a long lived fix.