[jira] [Closed] (ARCHETYPE-475) Each template file should have its own Velocity context

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov closed ARCHETYPE-475.
------------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Each template file should have its own Velocity context
> -------------------------------------------------------
>
>                 Key: ARCHETYPE-475
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-475
>             Project: Maven Archetype
>          Issue Type: Improvement
>          Components: Generator
>    Affects Versions: 2.2
>            Reporter: Christian Schlichtherle
>            Priority: Minor
>
> Right now, when generating a project from an archetype, all template files are merged with the same Velocity context. This has the side effect that changes to the Velocity context in one template file are reflected in all subsequent template files. Consider the following example:
> {code}
> #set ($foo = "bar")
> {code}
> This is a change to the Velocity context. Once it has been done, it's visible in all template files which get subsequently merged with the global Velocity context. This is bad because it's unexpected and uncontrollable because users have no control over the order of processing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)