Deprecate GuavaComponentRule #252
Merged
Conversation
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
jjohannes
force-pushed
the
251-deprecate-GuavaComponentRule
branch
from
9017302 to
612835a
Compare
It does no longer fit the current Guava release, which replaced jsr305 with jspecify. Users can use the patch DSL if needed. The rule will be removed in the next major release.
britter
force-pushed
the
251-deprecate-GuavaComponentRule
branch
from
612835a to
c9273e0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It does no longer fit the current Guava release, which replaced jsr305 with jspecify. Users can use the patch DSL if needed. The rule will be removed in the next major release.
Resolves #251