Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 58628 invoked by uid 500); 15 Mar 2001 23:49:15 -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 58359 invoked from network); 15 Mar 2001 23:49:07 -0000 Message-ID: <67FE02381F67D3119F960008C7845A2C0565A77E@nt_syd_ex09.macbank> From: Tim Vernum To: "'ANT-dev'" Subject: [Ant2] Feature requests Date: Fri, 16 Mar 2001 10:45:57 +1100 X-Mailer: Internet Mail Service (5.5.2650.21) X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N 1) Dynamically generated build files. I think that is covered by this point: allow facilities to build projects from multiple sources. ie CSS+xml or XSLT+ XML or Velocity+text or database or from inside jars or normal build.xmls etc. But I want to make sure. 2) Allow more customisation of filesets programmatically (ie from java) There are a number of points covering this in section V, but they're all quite specific, and are have the potential to be rejected. At the very basic level, what I want is for FileSet to be an interface so that I can (programmatically) generate a fileset that (eg) builds a list of filenames from a unix command. 3) As in (2), focus on making all datatypes interfaces, rather than the classes they are now, to allow for weird and wonderful customisations. 4) Releated to (2), allow "typedefs" similar to "taskdefs" so one can do " ... " I think that's the core things I want. Basically, I'm happy to hack up, all the features that I need, but I need the core to provide the interfaces/hooks to support that.