You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/01/04 13:46:40 UTC

[jira] [Commented] (DOXIASITETOOLS-144) split default-site.vm into 2 parts: default-site.vm and default-macros.vm

    [ https://issues.apache.org/jira/browse/DOXIASITETOOLS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081108#comment-15081108 ] 

Michael Osipov commented on DOXIASITETOOLS-144:
-----------------------------------------------

I assume you want to improve this on a per-skin basis, right? The macro signatures might be the same but the content produced varies from skin to skin.

> split default-site.vm into 2 parts: default-site.vm and default-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-macros.vm}} and parsing it from {{default-site.vm}} with some {{#parse( "default-macros.vm" )}} would IMHO improve maintenance



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)