[jbosstools-issues] [JBoss JIRA] (JBIDE-20491) "incompatibleImprovements" setting should be set

[Daniel Dekany (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-20491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254385#comment-13254385 ] 

Daniel Dekany commented on JBIDE-20491:
---------------------------------------

For the FreemarkerTestUtils issue, see: https://github.com/jbosstools/jbosstools-freemarker/pull/60

> "incompatibleImprovements" setting should be set
> ------------------------------------------------
>
>                 Key: JBIDE-20491
>                 URL: https://issues.jboss.org/browse/JBIDE-20491
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: freemarker
>            Reporter: Daniel Dekany
>            Assignee: Denis Golovin
>             Fix For: 4.4.1.S116
>
>
> Where the {{freemarker.template.Configuration}} is created, the {{incompatibleImprovements}} setting shouldn't be left on its default, 2.3.0. It should be set to {{Configuration.getVersion()}} (like {{new Configuration(Configuration.getVersion())}}, or with {{config.setIncompatibleImprovements(Configuration.getVersion())}}).
> Why: The plugin doesn't execute the templates, just parses them. As of 2.3.24, all the "incompatible" fixes that affect the parser (not the execution) just makes it stricter by eliminating legacy parser glitches that let through things that are pretty much always just user oversights. Also when 2.3.24 is out, the new {{ftlh}} and {{ftlx}} file extensions, which affect parsing, will only have effect with {{incompatibleImprovements}} 2.3.24.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)