You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a zero warnings policy for Java code (and yes, our code has zero warnings with custom Eclipse, Checkstyle and Findbugs profiles). Unfortunately, checkstyle still can't deal with type annotations on varargs (checkstyle/checkstyle#3238), so we have checkstyle exception markers on every file where such an annotation is used on a vararg, since we started introducing more Nullable/NonNull annotations in Eclipse.
I therefore propose an additional eclipse-cs workspace preference (checkbox) to control whether checkstyle exceptions shall be reported as problem markers on the respective files. Default value would be checked, to stay with todays behaviour. Logging in the error log would not be changed by this preference.
The text was updated successfully, but these errors were encountered:
We have a zero warnings policy for Java code (and yes, our code has zero warnings with custom Eclipse, Checkstyle and Findbugs profiles). Unfortunately, checkstyle still can't deal with type annotations on varargs (checkstyle/checkstyle#3238), so we have checkstyle exception markers on every file where such an annotation is used on a vararg, since we started introducing more Nullable/NonNull annotations in Eclipse.
I therefore propose an additional eclipse-cs workspace preference (checkbox) to control whether checkstyle exceptions shall be reported as problem markers on the respective files. Default value would be checked, to stay with todays behaviour. Logging in the error log would not be changed by this preference.
The text was updated successfully, but these errors were encountered: