[
https://issues.apache.org/jira/browse/DOXIA-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated DOXIA-677:
--------------------------------------
Description:
Many time we use Velocity only for resolving project properties like:
{code}
${project.version}
{code}
Another case is that for Markdown we have conflicts
Velocity uses # as a prefix for macros and ## as a prefix for comments
but in Markdown those are used for headers
So Doxia macro will be useful is such cases.
was:
Many time we use velocity only for resolving project properties like:
{code}
${project.version}
{code}
Another case is that for Markdown we have conflicts
Velocity uses # as a prefix for macros and ## as a prefix for comments
but in Markdown those is used for headers
So Doxia macro will be useful is such cases.
> Macro for printing project properties
> -------------------------------------
>
> Key: DOXIA-677
> URL: https://issues.apache.org/jira/browse/DOXIA-677
> Project: Maven Doxia
> Issue Type: New Feature
> Reporter: Slawomir Jaranowski
> Priority: Major
>
> Many time we use Velocity only for resolving project properties like:
> {code}
> ${project.version}
> {code}
> Another case is that for Markdown we have conflicts
> Velocity uses # as a prefix for macros and ## as a prefix for comments
> but in Markdown those are used for headers
> So Doxia macro will be useful is such cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
