Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 19217 invoked by uid 500); 24 Mar 2001 01:32: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 19195 invoked from network); 24 Mar 2001 01:32:49 -0000 From: David Rees To: ant-dev@jakarta.apache.org Subject: Re: Ant2 Feature Request Date: Fri, 23 Mar 2001 17:31:22 -0800 Reply-To: d.rees.l@usa.net Message-ID: References: <001701c0af54$bdea81b0$1e01a8c0@athena> <3AB42E6E.60507@i2.com> In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On 22 Mar 2001 09:34:28 +0100, Stefan Bodewig wrote: >Stefan Bodewig wrote: > >> David Rees wrote: >>=20 >>> Actually, what I would like to suggest is that we reify the idea of >>> a "task context". >>=20 >> David, just to let you know why I did not add this to the Ant2 wish >> list: This seems to be an implementation issue - or I'm >> misunderstanding your idea. > >Thinking about it once again - there are so many implementation issues >on the list already, that it wouldn't be fair to omit your suggestion. > I actually do consider it a feature in two ways. 1) Its clearly a feature for the API given to developers. To be honest this and a clean XML api that coincides with the code API is all I care about. The rest will all come in time. 2) I think it would be visible in the XML as well. Not clear what it would look like yet. d