Replace Xlint deprecation check with custom errorprone check #8061
+601
−294
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.
Motivated by #8060 (well, that and the many PRs in the instrumentation repo where this has plagued me recently)
Context:
When compiling with
--release 8, javac's-Xlint:deprecationwarns on imports of deprecated classes (JDK-8032211). Since@SuppressWarningscannot suppress import-level warnings, this forced us to use fully-qualified class names as a workaround.