Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 52886 invoked by uid 500); 23 May 2001 13:51:27 -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 52863 invoked from network); 23 May 2001 13:51:24 -0000 Message-ID: <3B0BC067.EBC8E5D9@digitalfocus.com> Date: Wed, 23 May 2001 09:51:35 -0400 From: Daniel Barclay X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: ant-dev@jakarta.apache.org Subject: Re: [DISC] details of task library concept References: <002501c0e2a9$fcfc56c0$9367883e@viquity.com> <3B0A896A.270EE970@digitalfocus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Stefan Bodewig wrote: > > Daniel Barclay wrote: > > > Stefan Bodewig wrote: > >> > > ... > >> But we've been thinking about something like an ANT_HOME/ext > >> directory where all tasks libraries living there would > >> automatically be detected and added by Ant. > > > > Would we need a separate directory (from $ANT_HOME/lib)? > > Not really, it may be nice if you could see what is part of your Ant > installation and what has been installed as a separate library. Oh, okay. Yeah, separation of Ant-supplied libraries/tasks/files from add-on libraries/tasks/files sounds good. (Separating tasks files from other library files probably isn't needed.) Daniel -- Daniel Barclay Digital Focus Daniel.Barclay@digitalfocus.com