lightguard.jp wrote

[...]I'm actually wondering now if it would be
better to simply instantiate the asciidoctor object in java and not worry
about the little ruby script. Thoughts on that approach?

Granted that I'm not a specialist, I'll go for the way that provides best integration with actual and future asciidoctor environment and features.
I mean if asciidoctor loads resources from ruby environment, I'd look for a way that gives to the jvm similar access to whatever resources it needs, namely backends, configuration and so on (possibly enabling the distribution of mandatory and optional artifacts along with the library or accessible companions).

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Is-it-worth-refactoring-asciidoctor-jruby-integration-into-a-shared-library-tp25p27.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML