>>>I recently went through our build files, changing all the >>>single-element uses of <if> into the above style.
I did something like that--and got bitten. 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). In those cases, you need the if-test to be in an element enclosing (and therefore, protecting) the inner element which is referencing a property which might not be defined. Merrill ------------------------------------------------------- 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
