[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065472#comment-15065472
]
Hudson commented on DOXIASITETOOLS-131:
---------------------------------------
SUCCESS: Integrated in doxia-all #198 (See
[https://builds.apache.org/job/doxia-all/198/])
[DOXIASITETOOLS-131] better management of Velocity context for the 2 use cases:
Doxia source ".vm" and template merging (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1720954])
*
./doxia-sitetools/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
* ./doxia-sitetools/doxia-site-renderer/src/site/apt/index.apt
> don't add Template-specific variables in general document Velocity context
> --------------------------------------------------------------------------
>
> Key: DOXIASITETOOLS-131
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-131
> Project: Maven Doxia Sitetools
> Issue Type: Task
> Components: Site renderer
> Affects Versions: 1.2, 1.6
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Fix For: 1.7
>
>
> Velocity is used in 2 different situations:
> - when evaluating a Doxia source file ending in ".vm"
> - when merging generated document output to site template
> some variables in Velocity context have a meaning only when merging template
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
