You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2022/10/08 11:42:00 UTC

[jira] [Updated] (DOXIA-677) Macro for printing project properties

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