FindBugs / Feature Requests / #284 Support @CheckForNull, @Nonnull, and @Nullable with any fully qualified name

#284 Support @CheckForNull, @Nonnull, and @Nullable with any fully qualified name

Milestone: 2.0.3

Status: closed-fixed

Owner: Andrey Loskutov

Labels: None

Priority: 5

Updated: 2014-06-19

Created: 2013-02-06

Creator: thinkpuppet

Private: No

We have used Guava and JSR305 together extensively, but in our current project cannot use JSR305. It would be awesome if FindBugs could check nullability issues using annotations for which the simple class name is @CheckForNull, @Nonnull, or @Nullable, regardless of the fully qualified class name.

We use home grown matching annotations and can configure our IDE to support them, but not FindBugs.

Discussion

Tagir Valeev - 2013-10-29

Vote for this ticket. Eclipse supports specifying custom classes as @NonNull and @Nullable annotations and we're actually using it (though Eclipse null analysis is very poor). It would be nice if FindBugs support user-specified class names for these annotations.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andrey Loskutov - 2014-06-19

status: open --> closed-fixed

assigned_to: Andrey Loskutov

Group: 3.0.0 --> 2.0.3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andrey Loskutov - 2014-06-19

Schould be fixed in 2.0.3, please validate.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andrey Loskutov - 2014-06-19

See https://code.google.com/p/findbugs/source/detail?r=ee8ac7f4b214857cdac028ad146048c0e69082a1

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Support @CheckForNull, @Nonnull, and @Nullable with any fully qualified name

Group

Searches

Help

#284 Support @CheckForNull, @Nonnull, and @Nullable with any fully qualified name

Discussion