[prev in list] [next in list] [prev in thread] [next in thread] 

List:       velocity-dev
Subject:    [jira] [Resolved] (VELOCITY-920) ParseErrorException with square brackets without leading space in v
From:       "Claude Brisson (Jira)" <jira () apache ! org>
Date:       2019-11-01 16:20:00
Message-ID: JIRA.13264213.1571910756000.78850.1572625200210 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/VELOCITY-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Claude Brisson resolved VELOCITY-920.
-------------------------------------
    Fix Version/s: 1.7.x
         Assignee: Claude Brisson
       Resolution: Not A Bug

Since Velocity 1.7, you have to use the formal notation for such situations:
{code}
${methodName}[]
{code}

> ParseErrorException with square brackets without leading space in velocity 2.1 from \
>                 1.4
> ---------------------------------------------------------------------------------------
>  
> Key: VELOCITY-920
> URL: https://issues.apache.org/jira/browse/VELOCITY-920
> Project: Velocity
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: swati agarwal
> Assignee: Claude Brisson
> Priority: Major
> Fix For: 1.7.x
> 
> Attachments: HelloWorld.java, helloworld.vm
> 
> 
> I have upgraded from velocity 1.4 to velocity-engine-core 2.1.
> I have also added the properties for backward compatibilty as mentioned in the page \
> https://velocity.apache.org/engine/2.1/upgrading.html. However, with the new jar I \
> am getting parse exception with the getTemplate method for vm file having content \
> '$methodName[]'. This was working with velocity 1.4



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]