maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schlichtherle (JIRA)" <j...@codehaus.org>
Subject [jira] (ARCHETYPE-475) Each template file should have its own Velocity context
Date Tue, 03 Feb 2015 00:02:18 GMT

    [ https://jira.codehaus.org/browse/ARCHETYPE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362410#comment-362410
] 

Christian Schlichtherle commented on ARCHETYPE-475:
---------------------------------------------------

Sorry, it seems I won't have some time to spend on this within a reasonable time frame.

> Each template file should have its own Velocity context
> -------------------------------------------------------
>
>                 Key: ARCHETYPE-475
>                 URL: https://jira.codehaus.org/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
(v6.1.6#6162)

Mime
View raw message