jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Delacretaz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-4301) get rid of JSR 305 dependency
Date Wed, 23 May 2018 11:04:00 GMT

    [ https://issues.apache.org/jira/browse/JCR-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487078#comment-16487078
] 

Bertrand Delacretaz commented on JCR-4301:
------------------------------------------

EPL is Category B as per https://www.apache.org/legal/resolved.html , such dependencies are
ok if included in binary form only. The Oak releases won't even include them, just have them
as dependencies so I think you're fine.

> 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)

Mime
View raw message