[
https://issues.apache.org/jira/browse/JCR-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507870#comment-16507870
]
Julian Reschke edited comment on JCR-4301 at 6/28/18 11:15 AM:
---------------------------------------------------------------
We recently discussed this on the phone, and [~anchela] suggested to introduce
our own annotations (in a new top-level Jackrabbit project) so that we can keep
the same annotation class names (and only have to update the import statements).
EDIT: note that there's no inheritance for annotations, so we'd need to rely on
checkers to be either configurable or lax with respect to checking package
names.
was (Author: reschke):
We recently discussed this on the phone, and [~anchela] suggested to introduce
out own annotations (in a new top-level Jackrabbit project) so that we can keep
the same annotation class names (and only have to update the import statements).
> 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
> Fix For: 2.18, 2.17.4
>
> Attachments: JCR-4301-2.diff, JCR-4301.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)
