Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 81928 invoked by uid 500); 15 Jun 2001 09:10:50 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 81770 invoked from network); 15 Jun 2001 09:10:48 -0000 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org Subject: Re: Problems with licenses (GPL, LGPL) and task writing References: From: Stefan Bodewig Date: 15 Jun 2001 11:10:56 +0200 In-Reply-To: Jirtme Lacoste's message of "Fri, 15 Jun 2001 10:57:05 +0200" Message-ID: Lines: 17 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Jirtme Lacoste wrote: > If I have a tool written under the GPL or LGPL, and I want to write > a task for it, shouldn't the license of the task be still GPL or > LGPL? Hmm, people have very different opinions on that. Things are quite clear if the original code is GPLed - as long as you directly use the tools classes/methods (without reflection), your code has to be GPLed as well. > In that case, can the task be part of the Ant optional tasks tree, > or is there a license conflict? If it is (L)GPLed, it cannot live in any Apache CVS module. Stefan