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

2.0.3
closed-fixed
None
5
2014-06-19
2013-02-06
thinkpuppet
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

  • Lany
    Lany
    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.

     
    • status: open --> closed-fixed
    • assigned_to: Andrey Loskutov
    • Group: 3.0.0 --> 2.0.3
     
  • Schould be fixed in 2.0.3, please validate.