The annotated element might be null, and uses of the element should check for null. When this annotation is applied to a method it applies to the method return value.

This annotation is used to denote a method whose return value should always be checked after invoking the method.

Indicates that all members of the class or package should be annotated with the default value of the supplied annotation classes. This would be used for behavior annotations such as @NonNull, @CheckForNull, or @CheckReturnValue. In particular, you can use @DefaultAnnotation(NonNull.class) on a class or package, and then use @Nullable only on those parameters, methods or fields that you want to allow to be null.

This is same as the DefaultAnnotation except it only applys to fields.

This is same as the DefaultAnnotation except it only applys to methods.

This is same as the DefaultAnnotation except it only applys to method parameters.

The annotated element must not be null. Annotated fields must not be null after construction has completed. Annotated methods must have non-null return values.

The annotated element could be null under some circumstances. In general, this means developers will have to read the documentation to determine when a null value is acceptable and whether it is neccessary to check for a null value. FindBugs will treat the annotated items as though they had no annotation.

In pratice this annotation is useful only for overriding an overarching NonNull annotation.

Used to annotate a method that, if overridden, must (or should) be invoke super in the overriding method. Examples of such methods include finalize() and clone(). The argument to the method indicates when the super invocation should occur: at any time, at the beginning of the overriding method, or at the end of the overriding method. (This anotation is not implmemented in FindBugs as of September 8, 2006).

This annotation is deprecated. Use CheckForNull instead.

The set of warnings that are to be suppressed by the compiler in the annotated element. Duplicate names are permitted. The second and successive occurrences of a name are ignored. The presence of unrecognized warning names is not an error: Compilers must ignore any warning names they do not recognize. They are, however, free to emit a warning if an annotation contains an unrecognized warning name. Compiler vendors should document the warning names they support in conjunction with this annotation type. They are encouraged to cooperate to ensure that the same names work across multiple compilers.

Used to indicate that the nullness of the target is unknown, or my vary in unknown ways in subclasses.

Used to indicate that the nullness of the target is unknown, or my vary in unknown ways in subclasses.