Let us summarize the behavior in question.
You have a template A which calls a macro M which in turn calls a
template B.
A defines $foo, B changes its value, and you want the new value to be
visible in A but not in M. Is that right?
Not quite. In Velocity 1.7 unless M also sets this value too before
calling B there is no reason it does not end up with what B have set.
Right. And that's even worse. We can't and don't want to reproduce that,
even with compatibility flags. Seriously, it can only break ill-formed
code. But ok, I'll include something in the upgrade page about that.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
