ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jose Alberto Fernandez <>
Subject RE: [PATCH] Minor fix for bug in Property task
Date Tue, 25 Jul 2000 19:15:25 GMT
> From: Stefan Bodewig []
> >>>>> "JAF" == Jose Alberto Fernandez <> writes:
>  JAF> Why don't we add (the people clammoring for mutable tasks) a new
>  JAF> task
>  JAF> <mutate property="abc" value="newXYZ value">
> Could be a solution. But if we are going to switch back to mutable
> properties altogether (still possible) this isn't needed.
 Notice that I am not so sure mutability is the best of ideas (mutability
in the large sense. I feel differently about the "controled" mutability
by allowing things like parameters and being able to associate different
with different calls. This means that properties are not mutable but they
may be instantiates with different values on different invocations.

Notice that even on <ant> and <antcall> tasks it is not true that all
properties are inmutable. In particular "basedir" is modified within the
call, maybe others.
My point is that the same can happen for user variables.

Jose Alberto

View raw message