maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DOXIASITETOOLS-144) Split default-site.vm into 2 parts: default-site.vm and default-site-macros.vm
Date Sun, 06 Mar 2016 20:47:40 GMT

     [ https://issues.apache.org/jira/browse/DOXIASITETOOLS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov updated DOXIASITETOOLS-144:
------------------------------------------
    Description: 
{{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

  was:
{{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


> 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)

Mime
View raw message