[
https://issues.apache.org/jira/browse/ARCHETYPE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403396#comment-16403396
]
Hervé Boutemy commented on ARCHETYPE-475:
-----------------------------------------
Sorry Christian, this is a general auto-close that was done: IMHO, [~michael-o]
a link to the process would ease understanding => for the next yearly auto-close
then, Christian: you can't re-open?
If so, we'll have to check either if we can change the Jira setup to let
reporter re-open, or if we'll reopen it for you: I'll do it personnally.
Now, on the issue itself: I just read it (didn't see it previously), and I
think it's a good idea and should be easy to do. Are you interested in trying
to fix it yourself with me to help and merge?
> 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)
