[
https://issues.apache.org/jira/browse/YETUS-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145257#comment-15145257
]
Allen Wittenauer commented on YETUS-233:
----------------------------------------
OK, after a bit of playing, I remember exactly why this was done. There is a
bug in pegdown where unmatched _'s will result in it going into an infinite
loop. This causes mvn site:site to freak out as well.
While it's a pain to find the problem (mvn site:site provides zero hints),
technically in order to trigger unescaped _'s, the author of the release note
is claiming it is in markdown format.
I think we basically advertise that we're going to do rendering in markdown.
It's not really our issue if what processes our markdown breaks on what is
invalid markdown generated upstream from us: we're just the messenger.
> rdm release notes in markdown are corrupting underscores in some instances
> --------------------------------------------------------------------------
>
> Key: YETUS-233
> URL: https://issues.apache.org/jira/browse/YETUS-233
> Project: Yetus
> Issue Type: Bug
> Components: Release Doc Maker
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Attachments: YETUS-233.00.patch
>
>
> YETUS-62 includes the text {code}`plugin_usage`{code} but rdm turns it into
> {code}`plugin\_usage`{code}. If a release note claims to be markdown, we
> shouldn't do that conversion. Considering it was written for doxia, we need
> to see what happens in mvn site if we don't do that with some of the Hadoop
> JIRAs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
