Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <039801bf4468$67a33520$0bfea8c0@berlin>
From: "James Duncan Davidson" <james.davidson@eng.sun.com>
To: <tomcat-dev@jakarta.apache.org>
References: <384C1116.6D1DB7C1@eng.sun.com> <384D549F.289A4E92@apache.org>
 <384DFFD7.13ED6515@eng.sun.com> <384EAA98.E564ED64@apache.org>
 <384FD993.E8BEA86E@eng.sun.com> <3850E9D8.F724C36E@apache.org>
 <38515063.672436E9@eng.sun.com> <3851C0A8.DC022F1F@mytownnet.com>
Subject: Re: Ant
Date: Sat, 11 Dec 1999 21:38:12 -0800
Organization: Phhpt!
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> Another way to deal with this creative tension -- allow a project to
declare
> a particular directory or Jar file as containing project-specific tasks.
At
> startup time, every Java class found here that implements Task would be
> auto-magically added to the available tasks within this project.  (I
suppose
> you' d have to allow Ant to compile them if necessary.)
>
> Since so much of Ant is already based on the Java reflection API, I can't
> believe this would be very hard to do.  And it would let you keep the
> standard Ant task-set very generic.

Something along these lines feels better. I'd like to keep the core Ant set
of tasks to a generic minimum (or at least a sane set) and let people use
the taskdef (or something similar to the above) as an escape hatch.

.duncan