Return-Path: Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: (qmail 47322 invoked from network); 30 Mar 2011 07:19:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Mar 2011 07:19:12 -0000 Received: (qmail 55052 invoked by uid 500); 30 Mar 2011 07:19:10 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 54743 invoked by uid 500); 30 Mar 2011 07:19:01 -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 54736 invoked by uid 99); 30 Mar 2011 07:19:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2011 07:19:00 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ralph.goers@dslextreme.com designates 209.85.214.178 as permitted sender) Received: from [209.85.214.178] (HELO mail-iw0-f178.google.com) (209.85.214.178) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2011 07:18:52 +0000 Received: by iwn9 with SMTP id 9so1218245iwn.23 for ; Wed, 30 Mar 2011 00:18:31 -0700 (PDT) Received: by 10.231.117.36 with SMTP id o36mr934003ibq.64.1301469510983; Wed, 30 Mar 2011 00:18:30 -0700 (PDT) Received: from [192.168.10.132] (cpe-75-82-178-177.socal.res.rr.com [75.82.178.177]) by mx.google.com with ESMTPS id he40sm4178939ibb.16.2011.03.30.00.18.29 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Mar 2011 00:18:29 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: Building ASL code requiring LGPL 3rd party From: Ralph Goers In-Reply-To: Date: Wed, 30 Mar 2011 00:18:27 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <9A732864-2163-41B1-94F2-818FFF708D4E@dslextreme.com> References: <3B3A5D2C-6AF9-4B33-BBB8-99C8346CFAC3@mitre.org> <34667B37-A7C6-4BD3-9B24-B9F5E980FF9C@dslextreme.com> To: legal-discuss@apache.org X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org Right. I saw the optional at runtime but missed the required at build. = Indeed, that is not specifically covered. I have mixed feelings about = this, and while I wouldn't go so far as to say it is verboten I would = say that a) it is highly discouraged and b) it probably could be = refactored so that the build dependency could be eliminated as well - = which probably has the same effect as saying it isn't allowed. On Mar 29, 2011, at 8:01 PM, Greg Stein wrote: > "JTS becomes required to build & test Lucene/Solr" >=20 > I don't see how that fits under the "optional" terms. My read is that > a *required* LGPL library is verboten. >=20 > On Tue, Mar 29, 2011 at 22:23, Ralph Goers = wrote: >> What you are describing sounds exactly like what = http://www.apache.org/legal/resolved.html#optional was intended to = answer. You timing is pretty good since that issue was resolved and = added to the page roughly a week ago. >>=20 >> Ralph >>=20 >>=20 >> On Mar 29, 2011, at 10:36 AM, Smiley, David W. wrote: >>=20 >>> Hello. >>>=20 >>> I've been involved with Lucene & Solr for some time. I'm working on = enhancing its support for geospatial search. I have java code in a patch = in JIRA SOLR-2155 but I'm seeking that it get committed. The patch uses = the LGPL licensed Java Topology Suite (JTS) library for part of its = functionality. That part is segmented in the code such that if JTS is = not included with Lucene/Solr at runtime then Lucene/Solr will still = work, and even the rest of my patch that doesn't use it. I modified = Lucene/Solr's ant based build script to automatically downloads the JTS = jar so that Lucene/Solr with my patch will compile and tests will run. = This is triggered by default in the build -- i.e. JTS becomes required = to build & test Lucene/Solr. The patch *does not* cause JTS to be = included in any packaged deliverable of Lucene/Solr. >>>=20 >>> Will the inclusion of my patch as I described in Lucene/Solr violate = the terms of applicable licensed software, namely Apache & LGPL? This = is the key question I wish to get adjudicated by authorities at the ASF. = I've read these sources already, carefully: >>> http://www.apache.org/legal/resolved.html >>> = http://www.apache.org/legal/3party.html#transition-examples-lgpl >>> = http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200801.mbox/%3C= 768dcb2e0801240130v604f0088w5781db2d889f5581@mail.gmail.com%3E >>>=20 >>> These references are not 100% clear on this matter, but in my = opinion I get the sense that my approach is satisfactory. But IANAL = (I'm sure that comes up often on this list!), and uncertainly amongst at = least two others on the Lucene/Solr list remains. I wish to get this = settled. >>>=20 >>> Thanks. >>>=20 >>> ~ David Smiley >>> = --------------------------------------------------------------------- >>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org >>> For additional commands, e-mail: legal-discuss-help@apache.org >>>=20 >>=20 >>=20 >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org >> For additional commands, e-mail: legal-discuss-help@apache.org >>=20 >>=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org > For additional commands, e-mail: legal-discuss-help@apache.org >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org For additional commands, e-mail: legal-discuss-help@apache.org