Login  Register

Re: Is it worth refactoring asciidoctor-jruby integration into a shared library?

Posted by LightGuardjp on Mar 07, 2013; 4:44pm
URL: https://discuss.asciidoctor.org/Is-it-worth-refactoring-asciidoctor-jruby-integration-into-a-shared-library-tp25p26.html

That's an interesting idea. 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?


On Thu, Mar 7, 2013 at 9:25 AM, davide.cavestro [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Hi guys,
I've just discovered asciidoctor following Andres Almiray tweets: is it worth refactoring the asciidoctor-jruby integration from maven and gradle plugins into a separate subproject?
If you make it available as a separate reusable library for the jvm that could increment asciidoctor diffusion, enabling other exotic/foolish usages (such as sketching to produce a plugin providing asciidoc(tor) previews within Eclipse IDE internal browser without other external dependency other than that library).

Cheers
Davide


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-tp25.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML



--
Jason Porter
http://en.gravatar.com/lightguardjp