[
https://issues.apache.org/jira/browse/PLUTO-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Nicklous closed PLUTO-322.
--------------------------------
Resolution: Won't Fix
too old; won't fix
> Interpolate version numbers in Pluto website documentation
> ----------------------------------------------------------
>
> Key: PLUTO-322
> URL: https://issues.apache.org/jira/browse/PLUTO-322
> Project: Pluto
> Issue Type: Task
> Components: documentation
> Affects Versions: 1.1.0
> Environment: pluto-site code module
> Reporter: Elliot Metsger
> Priority: Minor
>
> The Pluto website documentation references specific version numbers in a
> number of places. It would be nice if we could do some sort of variable
> substitution on the documentation and have the proper version numbers be
> generated as part of the release.
> I don't think XML entities will work, because the Xpp3 parser used by Doxia
> doesn't have DOCDECL support.
> I think it will come down to creating a custom Velocity template and using
> the $StringUtils reference in the template to perform substitution on the
> $bodyContent.
> One of the consequences of automatic version numbering in our site
> documentation is when we cut a release candidate. The maven:release plugin
> will deploy our site with the new version numbers before the release has been
> approved, which is not desired behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
