[
https://issues.apache.org/jira/browse/JCR-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487370#comment-16487370
]
Konrad Windszus edited comment on JCR-4301 at 5/23/18 2:39 PM:
---------------------------------------------------------------
For Sling we only use {{javax.annotation.CheckForNull}} and
{{javax.annotation.Nonnull}} because no annotation has the same meaning as
{{javax.annotation.Nullable}} and nullable is not evaluated by any tools (for
further information look at
http://sling.apache.org/documentation/development/jsr-305.html#annotations).
was (Author: kwin):
For Sling we only use {{javax.annotation.CheckForNull}} and
{{javax.annotation.Nonnull}} because no annotation has the same meaning as
{{javax.annotation.Nullable}} (for further information look at
http://sling.apache.org/documentation/development/jsr-305.html#annotations).
> get rid of JSR 305 dependency
> -----------------------------
>
> Key: JCR-4301
> URL: https://issues.apache.org/jira/browse/JCR-4301
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-api
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Major
> Attachments: JCR-4301-2.diff, JCR-4301.diff
>
>
> We should consider getting rid of the JSR 305 dependency (see
> <https://blog.codefx.org/java/jsr-305-java-9/>). Note that we only used the
> annotations in a few recently changed APIs.
> Further note that we could use spotbugs as replacement for findbugs to detect
> problems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
