Option to export AsciiDoc doc strings

One of the attendees at Devoxx France proposed the idea of having an option in Asciidoclet to export all AsciiDoc doc strings to disk (i.e., export-docstrings). Exporting the strings would allow the content to be reused in other context or by other tools.

I really like this idea as a way to keep content DRY, especially if Javadoc is being treated as the canonical source of information for a portion of the documentation. It’s the inverse strategy to using the include tag.

I imagine that each doc string would be exported to a file that is named according to where the doc string originated (package name + [class name] + [method name]). These files would be exported to the build output adjacent to the javadoc directory.

[johncarl81]

I’ve started a new project to output the raw contents of Javadocs to files. This can be used as part of the toolchain to incorporate the javadocs from a project into the final documentation.

You can find this project here: https://github.com/johncarl81/outputdoclet I figure we should continue this discussion about requirements and capabilities there.

[manoelcampos]

Hello again @johncarl81,

I think that this pull request is a good start point. We can continue the discussion there.