On 1/11/07, Daniel John Debrunner <[EMAIL PROTECTED]> wrote:

Seems like we almost rely on that behaviour today, given we use param in
some of the calls to junit-oneclass, such as junit-jdbc4. I confirmed
that values set in param are reset with a simple experiment.

My concern was that a variable that isn't used every time might have a
value set by a previous antcall the next time it was invoked, in an
antcall where you didn't want that setting. If you tested it and it
resets it to have no value, then great. :-)

andrew

Reply via email to