[ http://issues.apache.org/jira/browse/VELOCITY-264?page=all ]
Henning Schmiedehausen resolved VELOCITY-264.
---------------------------------------------
Fix Version/s: 2.0
(was: 1.5)
Resolution: Later
Yes, this is due to the weird parser magic in respect to escaping and comments.
This is due to a really big cleanup in 2.0. For the moment, this is more of a
"don't try this at home, kid" problem. We also need to add a note to the docs
about this.
> Escaping in form of "$\!{foo}" does not work
> --------------------------------------------
>
> Key: VELOCITY-264
> URL: http://issues.apache.org/jira/browse/VELOCITY-264
> Project: Velocity
> Issue Type: Bug
> Components: Source
> Affects Versions: 1.4
> Environment: Operating System: All
> Platform: PC
> Reporter: oleg
> Priority: Minor
> Fix For: 2.0
>
>
> Below are the results of executing app_example1 with a modified "example.vm"
> file. The content of the example.vm is a copy-paste from Velocity Userâ??s
> Guide
> (see the URL). Note that "$\!{foo}" was rendered to "$!{", instead of
> "$!{foo}"
> as expected:
> D:\dev\velocity-1.4\examples\app_example1>type example.vm
> #set( $foo = "bar" )
> $\!foo
> $\!{foo}
> $\\!foo
> $\\\!foo
> D:\dev\velocity-1.4\examples\app_example1>example
> Using classpath: .;..\..\bin\velocity-1.4.jar;..\..\bin\velocity-dep-1.4.jar
> $!foo
> $!{
> $\!foo
> $\\!foo
> D:\dev\velocity-1.4\examples\app_example1>
> Surprisingly, I could really use this feature :) as I want to evaluate my
> template in two steps: cache the result of the first generic step and then
> reuse it to generate various final messages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
