[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429952#comment-16429952 ] ASF subversion and git services commented on LOG4J2-1802: - Commit f8e509452f6218116ba35b2b3458c9fc51c1166b in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=f8e5094 ] LOG4J2-1802: Convert layouts manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > Fix For: 3.0.0 > > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429953#comment-16429953 ] ASF subversion and git services commented on LOG4J2-1802: - Commit ffd4ab638fc353cc67f22ee3957db56dbe8a2c17 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ffd4ab6 ] LOG4J2-1802: Add changelog entry > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > Fix For: 3.0.0 > > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429936#comment-16429936 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 59a9c2d4dce1c5f034aabe87eb939196b775b42e in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=59a9c2d ] LOG4J2-1802: Convert garbage-free manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429934#comment-16429934 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 0a60a4ad7480e03d1f26bbcaa45a6fad69d9b7c4 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=0a60a4a ] LOG4J2-1802: Convert filters manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429933#comment-16429933 ] ASF subversion and git services commented on LOG4J2-1802: - Commit b53b8118dbcff25b0bc64fab5cab6fe1ea84163b in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=b53b811 ] LOG4J2-1802: Convert configuration manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429931#comment-16429931 ] ASF subversion and git services commented on LOG4J2-1802: - Commit a15df802c4fd253e9cddac18e8674cddca806213 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=a15df80 ] LOG4J2-1802: Convert JMX manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429932#comment-16429932 ] ASF subversion and git services commented on LOG4J2-1802: - Commit fe2601c101070b69503ac94ba63758995384a1b2 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=fe2601c ] LOG4J2-1802: Convert custom log levels manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429889#comment-16429889 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 77a3712df0364e73ae5aa7bbfaaab58c2f738efb in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=77a3712 ] LOG4J2-1802: Convert programmatic config manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429887#comment-16429887 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 8dea0f4fb1eef58b266874e5b14cf3955f4d739e in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=8dea0f4 ] LOG4J2-1802: Convert log4j 1.x migration page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429891#comment-16429891 ] ASF subversion and git services commented on LOG4J2-1802: - Commit fa0135e20a238cc22276e0a2a5c4b764359115f2 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=fa0135e ] LOG4J2-1802: Convert logging separation manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429892#comment-16429892 ] ASF subversion and git services commented on LOG4J2-1802: - Commit db18f5ada1c2141a1d9531b0186855dcbd66991e in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=db18f5a ] LOG4J2-1802: Convert webapps manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429888#comment-16429888 ] ASF subversion and git services commented on LOG4J2-1802: - Commit a6744a659cbbc2a0758fdade5fe3c2bc679fe34e in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=a6744a6 ] LOG4J2-1802: Convert plugins manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429861#comment-16429861 ] ASF subversion and git services commented on LOG4J2-1802: - Commit d39e4751fbdad254138de44292aeea22a418eaad in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=d39e475 ] LOG4J2-1802: Convert scala api manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429858#comment-16429858 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 71b1f20f68154d5138bdcc9c2d864ccc4a13f414 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=71b1f20 ] LOG4J2-1802: Convert thread context manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429855#comment-16429855 ] ASF subversion and git services commented on LOG4J2-1802: - Commit f000b5e336ff31e5046b9e8791a1b28190639c22 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=f000b5e ] LOG4J2-1802: Convert flow tracing manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429857#comment-16429857 ] ASF subversion and git services commented on LOG4J2-1802: - Commit c34fa7efaa75f41ecdbae5ca426c2529738f2d86 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c34fa7e ] LOG4J2-1802: Convert messages manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429856#comment-16429856 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 56eb7a040f259d814006088a79a884d411df48a9 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=56eb7a0 ] LOG4J2-1802: Convert markers manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429565#comment-16429565 ] Remko Popma commented on LOG4J2-1802: - Apparently wrapping is the default in source blocks unless reconfigured: https://github.com/asciidoctor/asciidoctor.org/blob/master/docs/_includes/listing-wrap.adoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429563#comment-16429563 ] Remko Popma commented on LOG4J2-1802: - I think there is an AsciiDoc option to make the code wrap when too long instead of running off the page. That’s probably a good idea. > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429519#comment-16429519 ] Matt Sicker commented on LOG4J2-1802: - I tried that, but it doesn't seem to work. It needs to be explicitly supported apparently. > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429517#comment-16429517 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 967ebdad81c522ccde808acf2c6889c18003eed0 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=967ebda ] LOG4J2-1802: Convert architecture page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429499#comment-16429499 ] Ralph Goers commented on LOG4J2-1802: - My understanding is that any file that ends with .vm will be processed by Velocity. Once the file is translated it will then be processed by the appropriate rendering engine. So if you just append .vm to the Asciidoc file you should be able to put Velocity macros in it. > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[
https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429489#comment-16429489
]
Matt Sicker commented on LOG4J2-1802:
-
Ok, seems like AsciiDoc macros are not what I was expecting. They're not really
for dynamic things like some of the velocity macros I was using in the
{{maven-dependencies.md.vm}} template. There is [an open
issue|https://github.com/asciidoctor/asciidoctor-maven-plugin/issues/299] to
add Velocity support to the AsciiDoc plugin when used like this. For now, I'll
leave this file in markdown.
> Convert documentation into AsciiDoc
> ---
>
> Key: LOG4J2-1802
> URL: https://issues.apache.org/jira/browse/LOG4J2-1802
> Project: Log4j 2
> Issue Type: Documentation
> Components: Documentation
>Reporter: Matt Sicker
>Assignee: Matt Sicker
>Priority: Major
>
> The xdoc system currently in place is difficult to use correctly (it expects
> proper XHTML, no block level elements inside inline level elements, the usual
> pedantry from an XHTML/XML validator) and is needlessly verbose for writing
> documentation.
> After experimenting with Markdown as an alternative to xdoc, it has not been
> powerful enough for our uses. AsciiDoc, however, does offer more features
> useful here without extending the markdown processor itself. This will also
> help unify documentation formats used in other Log4j projects.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429479#comment-16429479 ] ASF subversion and git services commented on LOG4J2-1802: - Commit d159edb62ac888f102d4f40f2f6ea5f10565be5b in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=d159edb ] LOG4J2-1802: Convert performance page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429470#comment-16429470 ] ASF subversion and git services commented on LOG4J2-1802: - Commit c6b4182d8b4d54beeb74feafa7232edebbd814c1 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=c6b4182 ] LOG4J2-1802: Convert runtime dependencies page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429469#comment-16429469 ] Matt Sicker commented on LOG4J2-1802: - I think it still does. That would probably require manual formatting of the code. Also, one thing I've noticed about using AsciiDoc with our existing site template is that we're missing some styling features. Things still render cleanly, it's just that some CSS may be needed to complete the migration. > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429236#comment-16429236 ] Remko Popma commented on LOG4J2-1802: - Some of the source code in the PDF used to run off the page. I haven’t checked recently though... > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429178#comment-16429178 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 15cd6ac1c7f1d6838994490c15d5e1bcc006d987 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=15cd6ac ] LOG4J2-1802: Convert FAQ to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429167#comment-16429167 ] Matt Sicker commented on LOG4J2-1802: - So far the output pdf looks about the same. I haven't examined asciidoc's pdf output anywhere yet though. > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429129#comment-16429129 ] Ralph Goers commented on LOG4J2-1802: - You might want to try that anyway and see which comes out better. > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429124#comment-16429124 ] Matt Sicker commented on LOG4J2-1802: - Good point. Thankfully, AsciiDoc supports PDF output as well, so if the maven site output doesn't work properly anymore, I can convert it to use AsciiDoc's native PDF support. > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429117#comment-16429117 ] Ralph Goers commented on LOG4J2-1802: - Please be sure to check the pdf when you are done and make sure it is still usable. > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429104#comment-16429104 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 05511e486137b135c80b3e4d32e9bc60023a3a8b in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=05511e4 ] LOG4J2-1802: Convert download page to asciidoc Also fixes v2.3 download link > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429103#comment-16429103 ] ASF subversion and git services commented on LOG4J2-1802: - Commit ee96440d5e58c92884680ce04f64960c4410cbab in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ee96440 ] LOG4J2-1802: Convert index page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429083#comment-16429083 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 0c47af7f22b4ab7b720d857fc482ef1fc6fabf4e in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=0c47af7 ] LOG4J2-1802: Convert appenders manual to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429047#comment-16429047 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 3323831043ddb2b0612f134380acbe8e02a1c76c in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=3323831 ] LOG4J2-1802: Convert api manual page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429046#comment-16429046 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 7bd1c4646e0d9b81580478361443baca50c47c38 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=7bd1c46 ] LOG4J2-1802: Add prettyprint support for asciidoc output > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429016#comment-16429016 ] ASF subversion and git services commented on LOG4J2-1802: - Commit e4733bac28d176a933834658f908af5d4f0fd63b in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=e4733ba ] LOG4J2-1802: Convert thanks page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428852#comment-16428852 ] ASF subversion and git services commented on LOG4J2-1802: - Commit ea311fe638fa89a21255e00625642eea262a6f76 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ea311fe ] LOG4J2-1802: Convert guidelines page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428838#comment-16428838 ] ASF subversion and git services commented on LOG4J2-1802: - Commit dea6d414c06f2740f4f57e9211be8e771ad4ecd6 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=dea6d41 ] LOG4J2-1802: Convert javastyle page to asciidoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428717#comment-16428717 ] Matt Sicker commented on LOG4J2-1802: - pandoc seems to be a useful tool for converting docs. It may be able to automate most of this. > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (LOG4J2-1802) Convert documentation into AsciiDoc
[ https://issues.apache.org/jira/browse/LOG4J2-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428656#comment-16428656 ] ASF subversion and git services commented on LOG4J2-1802: - Commit 57169eb889cc014fa0ddc1648931125f036e5c50 in logging-log4j2's branch refs/heads/master from [~jvz] [ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=57169eb ] LOG4J2-1802: Convert site pages to AsciiDoc > Convert documentation into AsciiDoc > --- > > Key: LOG4J2-1802 > URL: https://issues.apache.org/jira/browse/LOG4J2-1802 > Project: Log4j 2 > Issue Type: Documentation > Components: Documentation >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > The xdoc system currently in place is difficult to use correctly (it expects > proper XHTML, no block level elements inside inline level elements, the usual > pedantry from an XHTML/XML validator) and is needlessly verbose for writing > documentation. > After experimenting with Markdown as an alternative to xdoc, it has not been > powerful enough for our uses. AsciiDoc, however, does offer more features > useful here without extending the markdown processor itself. This will also > help unify documentation formats used in other Log4j projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
