Abstract proguard rules at package level #1247
Merged
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.
After some investigation on #1242, I've concluded that:
javax.annotations
has annotations included in the JSR305, which is a spec of annotations that help with IDEs or other tools to avoid software defects.com.google.errorprone
has annotations related to ErrorProne, a static analyzer with its own set of annotations like above.These annotations are not reflected at runtime in any shape or form so, it's safe to ignore them (unfortunately, libs cannot specify what to ignore or not on proguard, so we need to do this by hand).
This PR groups the two annotation packages.