There are cases where an error-prone is used to enforce security checks. This is done by making the particular @BugPattern() severity=ERROR.
However, the user is still able to @SuppressWarnings() effectively bypassing such enforcements. So instead we have a build-restricted @SuppressFooChecker annotation and disable ability to SuppressWarnings by making the BugPattern suppressable=false (this CL).
Original issue created by martynas@google.com on 2013-12-09 at 10:39 PM
Link to code review: https://codereview.appspot.com/39740043
Purpose of code changes:
There are cases where an error-prone is used to enforce security checks. This is done by making the particular @BugPattern() severity=ERROR.
However, the user is still able to @SuppressWarnings() effectively bypassing such enforcements. So instead we have a build-restricted @SuppressFooChecker annotation and disable ability to SuppressWarnings by making the BugPattern suppressable=false (this CL).