From dev-return-8097-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Sat Sep 24 06:25:06 2005 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 45380 invoked from network); 24 Sep 2005 06:25:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Sep 2005 06:25:05 -0000 Received: (qmail 78327 invoked by uid 500); 24 Sep 2005 06:25:03 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 77843 invoked by uid 500); 24 Sep 2005 06:25:00 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 77811 invoked by uid 99); 24 Sep 2005 06:25:00 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2005 23:25:00 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_POST,FROM_ENDS_IN_NUMS,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of aok123@bellsouth.net designates 205.152.59.72 as permitted sender) Received: from [205.152.59.72] (HELO imf24aec.mail.bellsouth.net) (205.152.59.72) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2005 23:25:07 -0700 Received: from ibm70aec.bellsouth.net ([65.80.200.112]) by imf24aec.mail.bellsouth.net with ESMTP id <20050924062438.UAOT1158.imf24aec.mail.bellsouth.net@ibm70aec.bellsouth.net> for ; Sat, 24 Sep 2005 02:24:38 -0400 Received: from [172.16.1.39] (really [65.80.200.112]) by ibm70aec.bellsouth.net with ESMTP id <20050924062437.ZKLP25845.ibm70aec.bellsouth.net@[172.16.1.39]>; Sat, 24 Sep 2005 02:24:37 -0400 Message-ID: <4334F125.8040806@bellsouth.net> Date: Sat, 24 Sep 2005 02:24:37 -0400 From: Alex Karasulu User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: legal-discuss@apache.org, dev@directory.apache.org Subject: [ApacheDS] Best way to manage a dependency on a JSR 28 jar? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hello, Over at Directory we have some questions regarding how we are to deal with a dependency on a JSR 28 jar. We need to impose a dependency on the SASL API RI jar. Here's a link to the JSR 28 page: http://www.jcp.org/aboutJava/communityprocess/final/jsr028/index2.html While consulting with Brett Porter, we looked around for a license and found this here: http://www.worldspot.com/jsr28/jsr28_bizterms.txt We had the following questions regarding our handling of this jar: 1). Can we distribute it inside a binary distribution? 2). Can we download it at build time from a maven repository? 3). Can we check the jar into the SVN repository at the ASF? If none of these are possible is there an alternative that will allow us to use this API while meeting the constraints of the license? Thanks, Alex