chore: Replace use of several deprecated methods/classes by their successors#6933
Merged
chore: Replace use of several deprecated methods/classes by their successors#6933
Conversation
…h their replacements
…en-compiler-plugin configuration forceJavacCompilerUse was introduced in the past as part of configuring Google ErrorProne. Google ErrorProne was (temporarily) removed in 2020, but even when introducing it again the current configuration instructions for using ErrorProne with maven no longer require this flag to be set as per https://errorprone.info/docs/installation So rather than using the new flag forceLegacyJavacApi it's better to remove it
Collaborator
|
Thanks! We'll include this with the 11.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Description of Change
While checking the buildlog of the 'update maven requirement to 3.6.3' efforts I spotted several deprecation warnings.
The deprecations within the MavenProject unfortunately do not appear to have a replacement (yet), but as a side-activity I've worked through the other deprecations in order to clean them out of the codebase.
Have test cases been added to cover the new functionality?
not applicable