You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/03/05 11:54:00 UTC
[jira] [Moved] (DOXIATOOLS-84) Parser: Emit Velocity directives and variables in special Sink events
[ https://issues.apache.org/jira/browse/DOXIATOOLS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus moved DOXIA-729 to DOXIATOOLS-84:
-------------------------------------------------
Component/s: Doxia Converter
(was: Module - Apt)
(was: Module - Xdoc)
Key: DOXIATOOLS-84 (was: DOXIA-729)
Project: Maven Doxia Tools (was: Maven Doxia)
> Parser: Emit Velocity directives and variables in special Sink events
> ---------------------------------------------------------------------
>
> Key: DOXIATOOLS-84
> URL: https://issues.apache.org/jira/browse/DOXIATOOLS-84
> Project: Maven Doxia Tools
> Issue Type: Improvement
> Components: Doxia Converter
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> Velocity is often used together with markup (https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering). When parsing markup including Velocity statements/directives and references those are included in the regular {{Sink.text(...)}} event. Therefore it is often incorrectly escaped when being emitted by a Sink.
> Although usually Velocity is supposed to be executed *before* markup is passed to a parser, there are cases where one wants to retain the Velocity statements and references in the markup (e.g. for converting from one format to another with https://maven.apache.org/doxia/doxia-tools/doxia-converter/). Therefore parsers should treat Velocity specially (to prevent incorrect escaping).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)