Return-Path: 
 <ant-dev-return-21557-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 37897 invoked from network); 18 Dec 2001 19:39:43 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 18 Dec 2001 19:39:43 -0000
Received: (qmail 17307 invoked by uid 97); 18 Dec 2001 19:39:44 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 17291 invoked by uid 97); 18 Dec 2001 19:39:44 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 17280 invoked from network); 18 Dec 2001 19:39:43 -0000
X-Authentication-Warning: bodewig.bost.de: bodewig set sender to
 bodewig@apache.org using -f
To: ant-dev@jakarta.apache.org
Subject: Re: IntrospectionHelper questions
References: <CLEMKEJLBJDGBHEDNCPHEEFFDKAA.adammurdoch_ml@yahoo.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: 18 Dec 2001 20:31:41 +0100
In-Reply-To: "Adam Murdoch"'s message of "Tue, 18 Dec 2001 12:49:12 +1000"
Message-ID: <m3wuzkl3z6.fsf@bodewig.bost.de>
Lines: 19
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.4 (Civil Service)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Tue, 18 Dec 2001, Adam Murdoch <adammurdoch_ml@yahoo.com> wrote:

> I'd like to split up building the element/attribute tree, and
> building the target/task tree into 2 separate stages.

I agree completely.  Another thing that doesn't really work right now,
that's what triggered thinking about it in the Ant1 context again, is
redefining existing task names with <taskdef> (we will create the task
and all child element instances using the existing task definition
instead of the user supplied one).

> What I'm unsure of is how much room we have to play in.

Not too much, I'd go so far to say that we can only fiddle with privat
and package privat areas and at least simulate the old behavior for
things that get exposed to public - this includes access to
references.

Stefan

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>