Document command line in readme.adoc

[rockyallen]

I came across #360 while searching for a way to run asciidoc-bibtex AND a Java extension at the same time.
First, can asciidoctorj do this, and what command line would I need?
Second, should the command line be documented in readme.adoc?

[mojavelinux]

The asciidoctorj command works exactly the same way as the asciidoctor command. The only difference is that the command ends in a "j".

That's not strictly true, because technically AsciidoctorJ reimplements the cli. However, I still feel strongly that AsciidoctorJ should be delegating to the Asciidoctor cli so it really is the same. See #193.

[rockyallen]

Thanks. Just re-read the readme, and it makes more sense now.
What I want can't be done from the CLI, but I can write my own program against the AsciidoctorJ API, use the SPI interface for the Java extensions, and the require mechanism for asciidoctor-bibtex.
I think.
Still worth a mention in the readme that there is a CLI-it currently only discusses the API.

[mojavelinux]

Thanks for compiling this list. - AsciidoctorJ cannot use Ruby extensions at all, other than the ones it has built in This is not true. AsciidoctorJ can load any Ruby script. You just pass a path to the requires cli flag (-r) or requires API option and it will execute that script using JRuby. This feeds an extension directly to Asciidoctor core, bypassing the AsciidoctorJ API. Many people are using this capability successfully. There's also a Groovy DSL for writing extensions, but now we're moving beyond the scope of this topic.

[msgilligan]

Are there instructions for how to render PlantUML with asciidoctorj command-line?

[robertpanzer]

It should be similar to the corresponding asciidoctor command:

$ asciidoctorj -r asciidoctor-diagram ...

[msgilligan]

Thanks, @robertpanzer , that command should probably be in the README -- that's really useful.