[
https://issues.jboss.org/browse/RF-12918?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-12918:
------------------------------------
The two issue mentioned in the description have been resolved, but two new issues are
preventing us from using the released version of asciidoctor:
#
https://github.com/asciidoctor/asciidoctor/issues/172
#
https://github.com/asciidoctor/asciidoctor/issues/173
We are currently using a fork of asciidoctor to generate the docbook xml, as described
in:
https://github.com/richfaces/docs/blob/master/contributing.asciidoc
Switch to using the asciidoctor plugin for asciidoc processing
--------------------------------------------------------------
Key: RF-12918
URL:
https://issues.jboss.org/browse/RF-12918
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: doc
Affects Versions: 5.0.0.Alpha1
Reporter: Brian Leathem
Assignee: Brian Leathem
Fix For: 5-Tracking
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
It is currently not possible to generate the RichFaces docbook xml from the asciidoc
source using asciidoctor. Two bugs hold us back from switching to asciidoctor:
#
https://github.com/asciidoctor/asciidoctor/issues/116
#
https://github.com/asciidoctor/asciidoctor/issues/222
When these asciidoctor issues have been resolved, we can switch the richfaces docs
project to generate the xml using the asciidoctor maven plugin.
Until then, the asciidoc is processed using the asciidoc command line as described in:
https://github.com/richfaces/docs/blob/master/conversion/src/main/bash/as...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira