jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-37) Use nullability annotation to enforce/document API contract
Date Wed, 16 May 2012 16:01:04 GMT

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

Julian Reschke commented on OAK-37:
-----------------------------------

bq. PS. The Maven dependencies should have a <scope>provided</scope> entry in
them. Otherwise they'll show up as transitive dependencies in downstream components. See for
example the bndlib dependency for an example of another annotation library we're using.

Done; see attachment. Should I go ahead and commit this, and see how it works in practice
once we add more annotations?
                
> Use nullability annotation to enforce/document API contract
> -----------------------------------------------------------
>
>                 Key: OAK-37
>                 URL: https://issues.apache.org/jira/browse/OAK-37
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, jcr, mk
>            Reporter: Michael Dürig
>            Assignee: Julian Reschke
>         Attachments: nullability.patch, nullability.patch
>
>
> In a discussion about exception handling on the dev list [1] Julian brough up the idea
of using nullability annotations in APIs. I think we should decide on which one to use and
start using them whereever apropriate. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message