Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 77676 invoked from network); 20 Apr 2000 11:45:43 -0000 Received: from smtp01do.de.uu.net (192.76.144.61) by locus.apache.org with SMTP; 20 Apr 2000 11:45:43 -0000 Received: from sbodewig.bost.de ([195.127.75.69]) by smtp01do.de.uu.net (5.5.5/5.5.5) with ESMTP id NAA03470 for ; Thu, 20 Apr 2000 13:45:36 +0200 (MET DST) Received: (from bodewig@localhost) by sbodewig.bost.de (8.9.3/8.9.3) id NAA21233; Thu, 20 Apr 2000 13:45:34 +0200 X-Authentication-Warning: sbodewig.bost.de: bodewig set sender to bodewig@bost.de using -f To: ant-dev@jakarta.apache.org Subject: Re: Ant Principles (Taskdef storage) References: From: Stefan Bodewig Date: 20 Apr 2000 13:45:34 +0200 In-Reply-To: "Kuiper, Arnout"'s message of "Thu, 20 Apr 2000 13:13:07 +0200" Message-ID: Lines: 16 User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N >>>>> "KA" == Kuiper, Arnout writes: KA> Put all the required classes of a task in the tasks jar-file. Yes, this is certainly the easiest solution. There will be tasks that depend on third party classes - like the JUnit task depends on JUnit itself. In such a case you will probably want to use that third party lib independent of Ant and will put it in your CLASSPATH anyway. So either the shared classes are valuable on their own and "deserve" a standalone JAR file or you put them into all the task JARs that need them. Right? That's fine with me. Stefan