Sorry, I oversaw the fact that replaceProperties(...) is called for
attributes of both tasks and nested elements (it would have been
a strange asymmetry). I just tested it the wrong way (stupid!).
But still, wouldn't it be nice for a Task implementor to have
the possibility to turn off property replacement for some
attributes? As long as it is documented it should be ok.
AFAIK at the moment, to implement this I have to install
my own main PropertyHelper overriding replaceProperties(string)
and catch expressions I don't want to be parsed with a prefix,
something like ":noparsing:$$xxx${${}yyy".
Stefano Marsili
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
