[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191828#comment-15191828
]
Hudson commented on DOXIASITETOOLS-144:
---------------------------------------
SUCCESS: Integrated in doxia-all #268 (See
[https://builds.apache.org/job/doxia-all/268/])
[DOXIASITETOOLS-144] Split default-site.vm into 2 parts: default-site.vm and
default-site-macros.vm to ease understanding and maintenance (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1734735])
*
./doxia-sitetools/doxia-site-renderer/src/main/resources/org/apache/maven/doxia/siterenderer/resources/default-site-macros.vm
*
./doxia-sitetools/doxia-site-renderer/src/main/resources/org/apache/maven/doxia/siterenderer/resources/default-site.vm
*
./doxia-sitetools/doxia-site-renderer/src/test/java/org/apache/maven/doxia/siterenderer/DefaultSiteRendererTest.java
> Split default-site.vm into 2 parts: default-site.vm and default-site-macros.vm
> ------------------------------------------------------------------------------
>
> Key: DOXIASITETOOLS-144
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-144
> Project: Maven Doxia Sitetools
> Issue Type: Wish
> Components: Site renderer
> Affects Versions: 1.6
> Reporter: Hervé Boutemy
>
> {{default-site.vm}} starts with a bunch of macro definitions: this makes the
> real HTML template hard to find, at the end of the file
> putting these macro definitions into a separate file like
> {{default-site-macros.vm}} and parsing it from {{default-site.vm}} with some
> {{#parse( "default-site-macros.vm" )}} would IMHO improve maintenance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
