You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2019/06/12 13:35:00 UTC
[jira] [Moved] (OAK-8398) Add nullable/notnull annotations for
jackrabbit security API extensions
[ https://issues.apache.org/jira/browse/OAK-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke moved JCR-4444 to OAK-8398:
------------------------------------------
Component/s: (was: jackrabbit-api)
Workflow: no-reopen-closed (was: no-reopen-closed, patch-avail)
Key: OAK-8398 (was: JCR-4444)
Project: Jackrabbit Oak (was: Jackrabbit Content Repository)
> Add nullable/notnull annotations for jackrabbit security API extensions
> -----------------------------------------------------------------------
>
> Key: OAK-8398
> URL: https://issues.apache.org/jira/browse/OAK-8398
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: angela
> Assignee: angela
> Priority: Major
>
> due to the missing nullable/notnull annotations and unspecific javadoc it's not always clear, if null params are allow and if null return values should be expected. adding the missing annotations will IMO clarify the API contract.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)