Return-Path: Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: (qmail 25222 invoked from network); 1 Apr 2010 16:55:24 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Apr 2010 16:55:24 -0000 Received: (qmail 48308 invoked by uid 500); 1 Apr 2010 16:55:24 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 48105 invoked by uid 500); 1 Apr 2010 16:55:22 -0000 Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: Reply-To: legal-discuss@apache.org List-Id: Delivered-To: mailing list legal-discuss@apache.org Received: (qmail 48098 invoked by uid 99); 1 Apr 2010 16:55:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 16:55:22 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tom.e.white@gmail.com designates 209.85.220.217 as permitted sender) Received: from [209.85.220.217] (HELO mail-fx0-f217.google.com) (209.85.220.217) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 16:55:16 +0000 Received: by fxm9 with SMTP id 9so1120296fxm.24 for ; Thu, 01 Apr 2010 09:54:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:received:message-id:subject:from:to :content-type; bh=VFZqckjEozCr/yNmH4Zvg1KTcvHSGmFIOqGbvwnKaao=; b=nho5LD4wsDwoV80PJSBj3EUCoYhaaSVtgV3HPpoPSESDLJwzooDxkHKc7y7gclFWVj alDvnq3tFPSNge8z/BegL4zBk9O99rcB8TUt1NNK3+UiuwEIGuNR1Lv+BaFUHpfNKn3/ JL6FrKvyTSJShV1LJav1IsWLWhUzJrs7ljcnE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=Mjl8Q5qOqSABaDdry2SCSkPO0EzppBS0OwymsdA3yngc1ZFRTKj6Cw5uvsqFSCD0zF gKnxn9CwNUnDW5Y5sFQF1YtW/p3B9a0ppNOq574L6YPUvzwZZQXuoHYKKBqGO/FQk+K9 lYwyybtHng00dvVDk7rAPxyic1lqTfaot54mI= MIME-Version: 1.0 Sender: tom.e.white@gmail.com Received: by 10.239.134.74 with HTTP; Thu, 1 Apr 2010 09:54:54 -0700 (PDT) Date: Thu, 1 Apr 2010 09:54:54 -0700 X-Google-Sender-Auth: cca57ac6b7d48c14 Received: by 10.239.142.20 with SMTP id e20mr74268hba.70.1270140894529; Thu, 01 Apr 2010 09:54:54 -0700 (PDT) Message-ID: Subject: JDiff tool extensions From: Tom White To: legal-discuss@apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, I've created a small JDiff [1] extension that excludes source with certain Hadoop annotations [2]. I would like to use this in the Hadoop build process so we can publish public API changes. JDiff is LGPL-licensed, but it is not included as a part of Hadoop - it is only used for a couple of very particular build operations. My question is: is it permitted to include the JDiff extension in the Hadoop source tree? My reading of [3] suggests that this may be allowed, but I wanted to get further clarification. Thanks, Tom [1] http://javadiff.sourceforge.net/ [2] https://issues.apache.org/jira/browse/HADOOP-6658 [3] http://www.apache.org/legal/resolved.html#build-tools --------------------------------------------------------------------- To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org For additional commands, e-mail: legal-discuss-help@apache.org