Re: Scope of scripts -> workaround

2006-04-28 Thread Alexey N. Solofnenko
y("expr", expr); eval(""+project.getProperty("expr")); doPrecond(); - 1) Setting a property "expr" to transport the script 2) Executing the script in the calling task "t" Note t

Re: Scope of scripts -> workaround

2006-04-28 Thread Peter Reilly
Executing the script in the calling task "t" >> Note that without the ""+ at the beginning of eval() it does not >> work >> >> I hope this helps others, like this it is possible to collect >> precondition code at a single place. >> >>

Re: Scope of scripts -> workaround

2006-04-28 Thread Marcel Ruff
not work I hope this helps others, like this it is possible to collect precondition code at a single place. But still I'm wondering about the scope of scripts ... thanks Marcel http://www.xmlBlaster.org Marcel Ruff wrote: Hi, i have defined a javascript function in a "

Re: Scope of scripts -> workaround

2006-04-28 Thread Alexey N. Solofnenko
Setting a property "expr" to transport the script 2) Executing the script in the calling task "t" Note that without the ""+ at the beginning of eval() it does not work I hope this helps others, like this it is possible to collect precondition code at a single place. Bu

Re: Scope of scripts -> workaround

2006-04-28 Thread Marcel Ruff
others, like this it is possible to collect precondition code at a single place. But still I'm wondering about the scope of scripts ... thanks Marcel http://www.xmlBlaster.org Marcel Ruff wrote: Hi, i have defined a javascript function in a "pre" task, but when i want to call it lat

Scope of scripts

2006-04-28 Thread Marcel Ruff
Hi, i have defined a javascript function in a "pre" task, but when i want to call it later i get: ReferenceError: "doPrecond" is not defined Here is the xml, i call it with 'ant y': - function doPrecond() { project.log("HELLO PRECOND"); } doPrecond();