Edit Question - KnowledgeHub

Title Body

I want to create custom annotations to suppress individual FindBugs warnings to make it easier to use them via code-completion. For example, this one ignores constructors that don't set all @Nonnull fields. @TypeQualifierDefault(ElementType.CONSTRUCTOR) @SuppressFBWarnings("NP_NONNULL_FIELD_NOT_INITIALIZED_IN_CONSTRUCTOR") @Retention(RetentionPolicy.CLASS) public @interface SuppressNonnullFieldNotInitializedWarning { } However, I still see the warning when using the annotation. public class User { @Nonnull private String name; @SuppressNonnullFieldNotInitializedWarning public User() { // "Nonnull field name is not initialized by new User()" } } I've tried different retention policies and element types, putting the annotation on the constructor and the class, and even @TypeQualifierNickname . This same pattern works to apply @Nonnull to all fields in a class. @Nonnull @TypeQualifierDefault(ElementType.FIELD) @Retention(RetentionPolicy.RUNTIME) public @interface FieldsAreNonnullByDefault { } FindBugs correctly displays a warning for code that assigns null to name . @FieldsAreNonnullByDefault public class User { private String name; public UserModel() { name = null; // "Store of null value into field User.name annotated Nonnull" } } I believe the problem is that @SuppressFBWarnings is not marked with @TypeQualifier while @Nonnull is, and thus @TypeQualifierDefault and @TypeQualifierNickname don't apply to it. But there must be some other mechanism to apply one annotation using another.

Tags (comma-separated) Cancel