sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konrad Windszus <>
Subject Re: JSR 305 annotations (nullability)
Date Tue, 15 May 2018 15:16:47 GMT
IMHO migration from JSR-305 to
is very painless, because the former evolved from the latter. You only need to adjust the
package name but the semantics of the annotations are the same. Also it has most probably
the best tooling/IDE support because those are by far the oldest nullability annotations (invented
by FindBugs before JSR-305 has even been started). Now they are actively maintained by the
spotbugs community. I currently fail to see a better alternative, but I am open to other suggestions.

> On 15. May 2018, at 17:12, Julian Reschke <> wrote:
> On 2018-05-15 16:39, Konrad Windszus wrote:
>> There are some ideas in <>
but not yet a solution, as even the proposed alternative spotbugs-annotations is not yet JSR-305
free (which might be problematic from a licensing point of view). But IMHO the spotbugs annotations
are the best alternative:
because they are not bound to a specific IDE and are still supported by spotbugs/findbugs.
The only thing I am not sure about is whether SonarQube natively supports spotbugs-annotations.
>> Konrad
> It seems everybody agrees on the goal to move away, however it's not clear what to move
to (see for instance, <>).
> Best regards, Julian

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message