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
I did try putting the @NonNullPacakge and was hoping it would @nonnull kind of condition for all method parameters (including for static methods)....but it didmt.
By theway where are the annotation processor code...please indicate that
The text was updated successfully, but these errors were encountered:
venkateshamurthy
changed the title
Not working - What libraries to add or Java-11 based application
Not working - What libraries to add for Java-11 based application
Aug 20, 2021
was hoping it would @nonnull kind of condition for all method parameters (including for static methods)....but it didmt.
Hi, where/how did you expect this non-nullity to manifest?
This is how it works:
there's no dedicated annotation processor for @NonNullPackage
instead, @NonNullPackage annotation is based on JSR-305's @TypeQualierDefault annotation (which is a JSR-305 annotation designed specifically for creating custom nullability annotations)
as a result, @NonNullPackage should be recognized by all processors that already handle JSR-305 (e.g. IntelliJ IDE, Kotlin compiler)
As to libraries which can handle JSR-305, I'd check SpotBugs (but I haven't checked it myself - to me, just IntelliJ & Kotlin support was enough).
PS. Actually, there already was a question similar to yours 2 years ago - please see my answer to this question.
I did try putting the @NonNullPacakge and was hoping it would @nonnull kind of condition for all method parameters (including for static methods)....but it didmt.
By theway where are the annotation processor code...please indicate that
The text was updated successfully, but these errors were encountered: