Gert Driesen wrote:
----- Original Message -----
From: <[EMAIL PROTECTED]>
...
<mkdir dir="${empty}"
if="${string::get-length(empty) != 0}" />
...
BUILD FAILED
C:\Projects\Eden4All\test.build(6,4):
An empty string is not a valid value for attribute 'dir' of <mkdir
... />.
...
The value of the if/unless attribute is not evaluated before the
initialization of other attributes or child elements, hence you still get
build errors when you specify invalid values for these other attributes.
I'm not sure if this is something we should change.
What are the arguments in favor of not changing it? This issue comes up
fairly frequently, not just for the mkdir task. That indicates that
many people expect the if attribute to be evaluated before any other
attribute. Shouldn't that be the rule, applicable to all tasks, with no
exceptions?
Gary
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
