Return-Path: 
 <oak-dev-return-1174-apmail-jackrabbit-oak-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org>
X-Original-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org
Delivered-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 93840CF04
	for <apmail-jackrabbit-oak-dev-archive@minotaur.apache.org>;
 Wed, 16 May 2012 16:01:30 +0000 (UTC)
Received: (qmail 10089 invoked by uid 500); 16 May 2012 16:01:28 -0000
Delivered-To: apmail-jackrabbit-oak-dev-archive@jackrabbit.apache.org
Received: (qmail 10058 invoked by uid 500); 16 May 2012 16:01:28 -0000
Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:oak-dev-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:oak-dev-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:oak-dev@jackrabbit.apache.org>
List-Id: <oak-dev.jackrabbit.apache.org>
Reply-To: oak-dev@jackrabbit.apache.org
Delivered-To: mailing list oak-dev@jackrabbit.apache.org
Received: (qmail 10024 invoked by uid 99); 16 May 2012 16:01:28 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 16:01:28 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 16:01:25 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 953467C77
	for <oak-dev@jackrabbit.apache.org>; Wed, 16 May 2012 16:01:04 +0000 (UTC)
Date: Wed, 16 May 2012 16:01:04 +0000 (UTC)
From: "Julian Reschke (JIRA)" <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: 
 <705514065.4460.1337184064612.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1928494900.2188.1332422782079.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (OAK-37) Use nullability annotation to
 enforce/document API contract
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/OAK-37?page=3Dcom.atlassian.jir=
a.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13276834=
#comment-13276834 ]=20

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 anothe=
r annotation library we're using.

Done; see attachment. Should I go ahead and commit this, and see how it wor=
ks in practice once we add more annotations?
               =20
> 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=C3=BCrig
>            Assignee: Julian Reschke
>         Attachments: nullability.patch, nullability.patch
>
>
> In a discussion about exception handling on the dev list [1] Julian broug=
h up the idea of using nullability annotations in APIs. I think we should d=
ecide on which one to use and start using them whereever apropriate.=20

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