Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
content-class: urn:content-classes:message
Subject: RE: Memory utilization on ANT 1.6.0
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Jan 2004 13:11:07 -0000
Message-ID: <747F247264ECE34CA60E323FEF0CCC0C0F5198@london.cellectivity.com>
Thread-Topic: Memory utilization on ANT 1.6.0
Thread-Index: AcPU/nBb1jrpOoQ+TnebO1LNdenO1AAH/IUw
From: "Jose Alberto Fernandez" <jalberto@cellectivity.com>
To: "Ant Developers List" <dev@ant.apache.org>

> From: Stefan Bodewig [mailto:bodewig@apache.org]=20
>=20
> Historically the tasks are doing so for a different reason.  In Ant=20
> < 1.6 task instances could get reused.  Say you have target A=20
> depending on B and somebody runs "ant A B", then B will get=20
> executed twice and reuse the instances created in the first=20
> execution on the second run.
>=20
> AFAIU task instances are no longer supposed to get reused=20
> that way in 1.6 and thus the guarding code should be obsolute now.
>=20

How does it work in 1.6? Does "ant A B" will still execute target "B"
twice?

I think we really need to define a clean-up hook-up for the tasks that
by default just removes the task from the RuntimeConfigurable or
UnknownElement
holder instance.=20

Do not know all the consequences, but it seem like the right kind of
thing
to do.

Jose Alberto

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