[jira] [Created] (VELOCITY-893) Calling macro with closing brace on newline throws ParseErrorException

2018-05-30 Thread Steve O'Hara (JIRA)
Steve O'Hara created VELOCITY-893: - Summary: Calling macro with closing brace on newline throws ParseErrorException Key: VELOCITY-893 URL: https://issues.apache.org/jira/browse/VELOCITY-893 Project: V

[jira] [Created] (VELOCITY-892) Method arguments conversions should be based on Type instead of Class

2018-05-30 Thread Thomas Mortagne (JIRA)
Thomas Mortagne created VELOCITY-892: Summary: Method arguments conversions should be based on Type instead of Class Key: VELOCITY-892 URL: https://issues.apache.org/jira/browse/VELOCITY-892 Proje

Re: [jira] [Commented] (VELOCITY-891) Upgrade to v2.0 causes parser failures

2018-05-30 Thread Greg Huber
Have you tried {{#set ($JQId = '#' + $Utils.getJQuerySelector($SparklineElementId))}} eg #set ($ok = '#' + 'ok') $ok then outputs #ok #set ($ok = "#" + 'ok') gives Failed to parse String literal at 2f336dfc-5fee-4e00-a58d-1b5a54729690:standard[line 1, column 13] org.apache.velocity.

[jira] [Commented] (VELOCITY-891) Upgrade to v2.0 causes parser failures

2018-05-30 Thread Steve O'Hara (JIRA)
[ https://issues.apache.org/jira/browse/VELOCITY-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495207#comment-16495207 ] Steve O'Hara commented on VELOCITY-891: --- Added the stack trace to the description

[jira] [Updated] (VELOCITY-891) Upgrade to v2.0 causes parser failures

2018-05-30 Thread Steve O'Hara (JIRA)
[ https://issues.apache.org/jira/browse/VELOCITY-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve O'Hara updated VELOCITY-891: -- Description: We are upgrading from v1.7 to v2.0 but have come across a problem almost immedi