sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konrad Windszus <konra...@gmx.de>
Subject Re: JSR 305 annotations (nullability)
Date Tue, 15 May 2018 14:39:28 GMT
There are some ideas in https://issues.apache.org/jira/browse/SLING-7312 <https://issues.apache.org/jira/browse/SLING-7312>
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: https://github.com/spotbugs/spotbugs/tree/release-3.1/spotbugs-annotations/src/main/java/edu/umd/cs/findbugs/annotations
<https://github.com/spotbugs/spotbugs/tree/release-3.1/spotbugs-annotations/src/main/java/edu/umd/cs/findbugs/annotations>,
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

> On 15. May 2018, at 15:26, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> Hi there,
> 
> does the Sling team have a plan how to move away from the JSR 305 annotations?
> 
> See
> 
> <http://sling.apache.org/documentation/development/jsr-305.html#annotations>
> 
> and
> 
> <https://blog.codefx.org/java/jsr-305-java-9/>
> 
> 
> It would probably good to coordinate with Jackrabbit Oak; see <https://issues.apache.org/jira/browse/OAK-7368>...
> 
> Best regards, Julian


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