Nicola Ken Barozzi wrote:
The fact is that we need to be able to run *any* task at init.
There are two options:
1) make all tasks runnable top-level
2) deprecate using top-level tasks and add an <init> tag
Why does everything have to be a task? I'd rather think
property and filesets to be as definitions with some
sort of scope.
IMO an init task is redundant, because you can always have
an init target. A destroy task is another matter, though
I'd rather think of defining "error handling targets" which
may include the possibility to define a target which is
always called on exit.
J.Pietschmann
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
