[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614884#comment-16614884 ] Andras Piros commented on OOZIE-2734: - Thanks for the contribution [~asalamon74]! +1 > 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 > Fix For: 5.1.0 > > Attachments: OOZIE-2734-1.patch, OOZIE-2734-10.patch, > OOZIE-2734-2.patch, OOZIE-2734-3.patch, OOZIE-2734-4.patch, > OOZIE-2734-5.patch, OOZIE-2734-6.patch, OOZIE-2734-7.patch, > OOZIE-2734-8.patch, OOZIE-2734-9.patch, oozie_generated_html_20180731.zip, > oozie_generated_html_markdown_20180802.zip, > oozie_generated_html_markdown_20180905.zip, > oozie_generated_html_markdown_20180910.zip, > oozie_generated_html_markdown_20180912.zip, > oozie_generated_html_markdown_20180913.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613617#comment-16613617
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 311 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:red}-1 RAT{color}
.{color:red}-1{color} the patch seems to introduce 1 new RAT warning(s)
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
There were errors during execution. Check console output for details.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/817/
> 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
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-10.patch,
> OOZIE-2734-2.patch, OOZIE-2734-3.patch, OOZIE-2734-4.patch,
> OOZIE-2734-5.patch, OOZIE-2734-6.patch, OOZIE-2734-7.patch,
> OOZIE-2734-8.patch, OOZIE-2734-9.patch, oozie_generated_html_20180731.zip,
> oozie_generated_html_markdown_20180802.zip,
> oozie_generated_html_markdown_20180905.zip,
> oozie_generated_html_markdown_20180910.zip,
> oozie_generated_html_markdown_20180912.zip,
> oozie_generated_html_markdown_20180913.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
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613421#comment-16613421 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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 > Fix For: 5.1.0 > > Attachments: OOZIE-2734-1.patch, OOZIE-2734-10.patch, > OOZIE-2734-2.patch, OOZIE-2734-3.patch, OOZIE-2734-4.patch, > OOZIE-2734-5.patch, OOZIE-2734-6.patch, OOZIE-2734-7.patch, > OOZIE-2734-8.patch, OOZIE-2734-9.patch, oozie_generated_html_20180731.zip, > oozie_generated_html_markdown_20180802.zip, > oozie_generated_html_markdown_20180905.zip, > oozie_generated_html_markdown_20180910.zip, > oozie_generated_html_markdown_20180912.zip, > oozie_generated_html_markdown_20180913.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16612386#comment-16612386 ] Andras Salamon commented on OOZIE-2734: --- We get the RAT warning because of the README.md file (which replaces the old README.txt). I think we can ignore it. > 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 > Fix For: 5.1.0 > > Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch, > OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch, > OOZIE-2734-6.patch, OOZIE-2734-7.patch, OOZIE-2734-8.patch, > OOZIE-2734-9.patch, oozie_generated_html_20180731.zip, > oozie_generated_html_markdown_20180802.zip, > oozie_generated_html_markdown_20180905.zip, > oozie_generated_html_markdown_20180910.zip, > oozie_generated_html_markdown_20180912.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611943#comment-16611943
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 312 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:red}-1 RAT{color}
.{color:red}-1{color} the patch seems to introduce 1 new RAT warning(s)
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
There were errors during execution. Check console output for details.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/816/
> 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
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch,
> OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch,
> OOZIE-2734-6.patch, OOZIE-2734-7.patch, OOZIE-2734-8.patch,
> OOZIE-2734-9.patch, oozie_generated_html_20180731.zip,
> oozie_generated_html_markdown_20180802.zip,
> oozie_generated_html_markdown_20180905.zip,
> oozie_generated_html_markdown_20180910.zip,
> oozie_generated_html_markdown_20180912.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
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611785#comment-16611785 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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 > Fix For: 5.1.0 > > Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch, > OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch, > OOZIE-2734-6.patch, OOZIE-2734-7.patch, OOZIE-2734-8.patch, > OOZIE-2734-9.patch, oozie_generated_html_20180731.zip, > oozie_generated_html_markdown_20180802.zip, > oozie_generated_html_markdown_20180905.zip, > oozie_generated_html_markdown_20180910.zip, > oozie_generated_html_markdown_20180912.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16608954#comment-16608954
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 311 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
There were errors during execution. Check console output for details.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/813/
> 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
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch,
> OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch,
> OOZIE-2734-6.patch, OOZIE-2734-7.patch, OOZIE-2734-8.patch,
> oozie_generated_html_20180731.zip,
> oozie_generated_html_markdown_20180802.zip,
> oozie_generated_html_markdown_20180905.zip,
> oozie_generated_html_markdown_20180910.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
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16608819#comment-16608819 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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 > Fix For: 5.1.0 > > Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch, > OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch, > OOZIE-2734-6.patch, OOZIE-2734-7.patch, OOZIE-2734-8.patch, > oozie_generated_html_20180731.zip, > oozie_generated_html_markdown_20180802.zip, > oozie_generated_html_markdown_20180905.zip, > oozie_generated_html_markdown_20180910.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604277#comment-16604277
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 281 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:orange}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/git].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [webapp].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2940
.{color:orange}Tests failed at first run:{color}
TestCoordActionsKillXCommand#testActionKillCommandDate
TestCoordMaterializeTriggerService#testCoordMaterializeTriggerService3
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/808/
> 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
> Fix For: 5.1.0
>
> Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch,
> OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch,
> OOZIE-2734-6.patch, OOZIE-2734-7.patch, oozie_generated_html_20180731.zip,
> oozie_generated_html_markdown_20180802.zip,
> oozie_generated_html_markdown_20180905.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
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604159#comment-16604159 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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 > Fix For: 5.1.0 > > Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch, > OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch, > OOZIE-2734-6.patch, OOZIE-2734-7.patch, oozie_generated_html_20180731.zip, > oozie_generated_html_markdown_20180802.zip, > oozie_generated_html_markdown_20180905.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604090#comment-16604090 ] Andras Salamon commented on OOZIE-2734: --- The recently committed OOZIE-2877 modified the twiki documentation, so I updated the markdown patch. > 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 > Fix For: 5.1.0 > > Attachments: OOZIE-2734-1.patch, OOZIE-2734-2.patch, > OOZIE-2734-3.patch, OOZIE-2734-4.patch, OOZIE-2734-5.patch, > OOZIE-2734-6.patch, OOZIE-2734-7.patch, oozie_generated_html_20180731.zip, > oozie_generated_html_markdown_20180802.zip, > oozie_generated_html_markdown_20180905.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580911#comment-16580911
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 281 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
error(s)
.{color:red}ERROR{color}: the current HEAD has 2 Javadoc error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2918
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/758/
> 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-2734-5.patch,
> OOZIE-2734-6.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580844#comment-16580844 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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-2734-5.patch, > OOZIE-2734-6.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580039#comment-16580039
]
Andras Piros commented on OOZIE-2734:
-
[~asalamon74] can you please look into the pre-commit issues, mainly why
{{DISTRO}} step keeps failing? Thanks!
> 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-2734-5.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16580034#comment-16580034
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 281 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2918
.{color:orange}Tests failed at first run:{color}
TestZKLocksService#testTimeoutTimingOutWriteLockOozies
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/756/
> 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-2734-5.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579946#comment-16579946 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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-2734-5.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579913#comment-16579913
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 281 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2918
.{color:orange}Tests failed at first run:{color}
TestCoordActionInputCheckXCommandNonUTC>TestCoordActionInputCheckXCommand#testNone
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/755/
> 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-2734-5.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579795#comment-16579795 ] Andras Salamon commented on OOZIE-2734: --- [~gezapeti] Thanks for checking. I've uploaded version5 of the patch which fixes the problem. It does not change the HTML output, so I don't uploaded the HTML files this time. > 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-2734-5.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579793#comment-16579793 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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-2734-5.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579691#comment-16579691
]
Peter Cseh commented on OOZIE-2734:
---
I get an error when I execute mvn clean install site:
{noformat}
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3.854 s
[INFO] Finished at: 2018-08-14T13:55:12+02:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7:site (default-site) on project
oozie-main: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.7:site failed: A required class
was missing while executing
org.apache.maven.plugins:maven-site-plugin:3.7:site:
org/apache/maven/doxia/sink/impl/XhtmlBaseSink
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.7
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
{noformat}
> 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578729#comment-16578729 ] Andras Salamon commented on OOZIE-2734: --- Thank you [~rkanter] for the tip. Next time I'll upload the HTML samples first and the patch only after that. > 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578148#comment-16578148
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 281 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2918
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/749/
> 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578064#comment-16578064 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578061#comment-16578061 ] Peter Cseh commented on OOZIE-2734: --- Reuploaded Patch-3 as patch-4 as a workaround. > 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578060#comment-16578060
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578058#comment-16578058
]
Peter Cseh commented on OOZIE-2734:
---
I've retriggered the job and the issue is:
{noformat}
Testing JIRA OOZIE-2734
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 129k0 129k0 0 172k 0 --:--:-- --:--:-- --:--:-- 172k
100 191k0 191k0 0 254k 0 --:--:-- --:--:-- --:--:-- 254k
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 621k 100 621k0 0 772k 0 --:--:-- --:--:-- --:--:-- 772k
JIRA OOZIE-2734, patch downloaded at Mon Aug 13 10:13:21 UTC 2018 from
https://issues.apache.org/jira/secure/attachment/12934086/oozie_generated_html_markdown_20180802.zip
{noformat}
So the precommit downloads the latest attachment. It's usually not a problem,
but in this case the ZIP does not applies as a patch. no surprise there.
> 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_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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578057#comment-16578057 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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_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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16569801#comment-16569801 ] Andras Salamon commented on OOZIE-2734: --- I've checked the patch again, I'm quite sure that the patch applies. Hopefully this comment will trigger Jenkins again. > 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_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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566847#comment-16566847
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> 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_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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566845#comment-16566845 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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_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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566842#comment-16566842 ] Andras Salamon commented on OOZIE-2734: --- I've uploaded a new set of generated HTML files. > 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_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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566735#comment-16566735 ] Peter Cseh commented on OOZIE-2734: --- Thanks for the work you've been put into this [~asalamon74]! I'll check this out soon > 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_generated_html_20180731.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566647#comment-16566647 ] Andras Salamon commented on OOZIE-2734: --- Thanks for checking [~pbacsko] my last patch (OOZIE-2734-3.patch) contains the fixes. > 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_generated_html_20180731.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566641#comment-16566641
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 281 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2912
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/715/
> 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_generated_html_20180731.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566558#comment-16566558 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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_generated_html_20180731.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563853#comment-16563853
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:red}-1{color} the patch contains 3 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 282 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
.{color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
.{color:green}+1{color} the patch does not seem to introduce new Javadoc
error(s)
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
. {color:green}+1{color} There are no new bugs found in [server].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [sharelib/distcp].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 2911
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/707/
> 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_generated_html_20180731.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563814#comment-16563814
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> 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_generated_html_20180731.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563810#comment-16563810 ] Andras Salamon commented on OOZIE-2734: --- I uploaded a zip which contains the HTML generated from the twiki and from the markdown documentation. > 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_generated_html_20180731.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563804#comment-16563804 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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_generated_html_20180731.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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563727#comment-16563727 ] Andras Salamon commented on OOZIE-2734: --- A few comments about my patch: * I've updated quite a few maven plugins used during the site creation, so we also address OOZIE-3164 * A customised version of the twiki pugin was used for HTML creation (because of special colors and table of contents), there is no need for a customised plugin for markdown * To avoid using a customised plugin I've changed a few header formatting levels. For instance twiki was using a header3 sometimes with a special flag to avoid the header to appear in the table of contents. I use a simple bold formatting instead. * HTML generation from Markdown is quite strict compared to the HTML generation from Twiki. If the input file is not syntactically correct sometimes it just gives an error message instead of creating a semi-correct HTML file. > 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, > 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563725#comment-16563725 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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, > 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[
https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561911#comment-16561911
]
Hadoop QA commented on OOZIE-2734:
--
Testing JIRA OOZIE-2734
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> 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, 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561904#comment-16561904 ] Hadoop QA commented on OOZIE-2734: -- PreCommit-OOZIE-Build started > 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, 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561715#comment-16561715 ] Andras Salamon commented on OOZIE-2734: --- I've tried the listed tools without much success. It might be a limitation of the tools, but the fact that the oozie twiki documentation contains errors is also a problem for the tools. Unfortunately sometimes it means that information is missing from the HTML version of the documentation, so using the HTML files as a source of the conversation is probably not the best idea. I created my own tool to convert the twiki documentations to markdown and handle the errors and special cases. The script uses sed (in retrospect it was not the best idea). I upload the current version of the script, but check it only at your own risk. > 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 > > 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445491#comment-16445491 ] Andras Piros commented on OOZIE-2734: - Most possibly it's best to convert TWiki to HTML first, then HTML to Markdown, for the sake of keeping manual effort to a bare minimum. > 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 >Priority: Major > > 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)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015000#comment-16015000 ] Robert Kanter commented on OOZIE-2734: -- Another option we shouldn't overlook is the newer maven-site-plugin. We're currently on some funny version of 2.x, but the latest version is 3.x and was presumably used to generate it's own website, which looks perfectly fine: https://maven.apache.org/plugins/maven-site-plugin/index.html. Looks like it supports a variety of formats: https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Documentation_formats > 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 > > 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 (v6.3.15#6346)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997397#comment-15997397 ] Robert Kanter commented on OOZIE-2734: -- The Apache Ignite docs look really nice, but it looks like they're actually hosted by http://readme.io, so I don't think that would work for us. I was also talking with [~gezapeti], and he tried out a few autoconverting tools and they weren't very good. It's probably best to just start from scratch. That would also allow whoever does it to reorganize things as they go through it, but they can still copy-paste large portions of the existing docs contents. > 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 > > 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 (v6.3.15#6346)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866706#comment-15866706 ] Rohini Palaniswamy commented on OOZIE-2734: --- Came across Apache Ignite documentation today - https://ignite.apache.org/ and it looks really good. We should check that out as well. > 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 > > 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 (v6.3.15#6346)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850701#comment-15850701 ] Rohini Palaniswamy commented on OOZIE-2734: --- It would also be good to integrate the following cwiki docs as part of the regular documentation during this exercise. They have very good information. https://cwiki.apache.org/confluence/display/OOZIE/Java+Cookbook https://cwiki.apache.org/confluence/display/OOZIE/Map+Reduce+Cookbook https://cwiki.apache.org/confluence/display/OOZIE/Pig+Cookbook > 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 > > 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 (v6.3.15#6346)
[jira] [Commented] (OOZIE-2734) Switch docs from twiki to markdown
[ https://issues.apache.org/jira/browse/OOZIE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849130#comment-15849130 ] Andras Piros commented on OOZIE-2734: - Look also at: * Apache Drill * Jekyll * AsciiDocs > 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 > > 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 (v6.3.15#6346)
