[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578657#comment-16578657
]
Robert Kanter commented on OOZIE-2734:
--------------------------------------
Oh yeah - that's a limitation we run into every so often. It always tries to
grab the newest attachement, and doesn't check the type. So it's best to
attach any other files first, and then the patch file last.
> Switch docs from twiki to markdown
> ----------------------------------
>
> Key: OOZIE-2734
> URL: https://issues.apache.org/jira/browse/OOZIE-2734
> Project: Oozie
> Issue Type: Improvement
> Components: docs
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Andras Salamon
> Priority: Major
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch,
> OOZIE-2734-3.patch, OOZIE-2734-4.patch, oozie_generated_html_20180731.zip,
> oozie_generated_html_markdown_20180802.zip, twiki2md_20180730.zip
>
>
> This won't be a fun JIRA, but it would be great if we could switch to
> something easier to work with and better supported like markdown, and get rid
> of the super old twiki we're using for docs.
> I found two tools that I haven't tried out that claim to be able to convert
> this for us:
> # http://pandoc.org/
> # https://github.com/jcodagnone/twiki2markdown
> The former supports a lot of different formats, and according to [this blog
> post|http://goer.org/Journal/2013/02/converting_twiki_foswiki_to_markdown_restructuredtext.html]
> it's better to convert from the rendered html instead of the twiki. But who
> knows which is better, or if the second tool is better than either.
> I think once we switch to a better format, it will be easier to keep the docs
> in better shape, as they could really use some reorganizing. Though we can
> keep that for a separate task.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
