[VELOCITY-504] Call to evaluate inside of macro fails with 1.5 beta2

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.5 beta2
• Fix Version/s: 1.5
• Component/s: Engine
• Environment: Windows XP, Sun J2SE 1.5.0_09
• Assignee: Henning Schmiedehausen
• Reporter: Reggie Riser
• Created: 28/Nov/06 22:32
• Updated: 26/Mar/07 05:02
• Resolved: 03/Jan/07 22:29

Description

When upgrading from 1.5 beta 1 to beta2, I ran into a problem with one of our macros that makes a call to Velocity.evaluate (via a tool) within a foreach loop. With beta 1, everything worked fine. But we get a "cannot be resolved" error with beta 2. The same code works fine outside of a macro with either version.

I've distilled the issue we're having down to a simple test case and have attached example code and a build file showing the problem. Just do an "ant beta1" or "ant beta2" to see how the results differ between beta1 and beta2.

Issue Links

• is related to: VELOCITY-509 Add new directive #evaluate