>From: "Merrill Cornish" <[EMAIL PROTECTED]>
>Sent: Thursday, July 29, 2004 3:03 PM
...
> The problem occurs if the if-test is checking for existence of a property
>name that the rest of the task is referencing. It appears that when entire
>task element is parsed (which exposes the undefined property) before
>the if-test is used to decide whether the task should be executed or not
>(which is reasonable from the parser's point of view).
Good point. It turns out the only case where I actually had that was also
a multiple task case, so I avoided the ant bite. Most of them were for
setting default values for a bunch of properties. (I wish NAnt had
bash's ${name:=default} shorthand.)
Gary
Gary
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
