Thomas Mortagne created VELOCITY-925:

             Summary: Macro calls without parenthesis now "eats" the following 
                 Key: VELOCITY-925
             Project: Velocity
          Issue Type: Bug
          Components: Engine
    Affects Versions: 2.1
            Reporter: Thomas Mortagne

The behavior of macro calls without parenthesis changed in 2.x. I cannot find 
anything in the changelog about that but maybe I missed it.

The following:



* in Velocity 1.7: "value/n"
* in Velocity 2.x: "value"



produces in both Velocity versions "value" (eats the newline)

Looks like omitting parenthesis in Velocity 1.7 was making the macro call 
"inline" while having them was eating the following newline like things like 
#set directive do.

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to