[
https://issues.apache.org/jira/browse/VELOCITY-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291853#comment-17291853
]
Al Bundy commented on VELOCITY-935:
-----------------------------------
is it really a wrong precedence in previous versions?
i know that Velocity supports #if ("$!foobar" ) to check if a string is empty
but is it really the same as a boolean-check or is it more kind of syntactic
sugar?
in my case I would first expect the string comparison and after that I would
expect the negation of the result.
but to be honest, i'm not sure myself what is right.
nevertheless I'll try to identify faulty templates.
> Negation dos not work correctly after update from 1.6 to 2.2
> ------------------------------------------------------------
>
> Key: VELOCITY-935
> URL: https://issues.apache.org/jira/browse/VELOCITY-935
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 2.2
> Reporter: Al Bundy
> Assignee: Claude Brisson
> Priority: Major
>
> With 1.6 we used this
>
> {code:java}
> #if ( ! "$!testrun" == "true" )
> ...
> #end{code}
> This ensures that the code is only executed if current run is not a testrun
> ($testrun false or empty).
>
> Sine update to 2.2 this does not to work.
> In my case $testrun was false, but code was not executed.
> To get this to work I had to use brackets around the equals-check
> {code:java}
> #if ( ! ("$!testrun" == "true") )
> ...
> #end
> {code}
> This breaks the logic of a lot of templates...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
