Posted by asotobu on Jul 01, 2013; 7:16pm
URL: https://discuss.asciidoctor.org/Latest-version-of-Asciidoctor-does-not-integrate-with-AJI-project-tp366.html

Today I can say that I am so happy, (although there are some bad news) and it is because the CI approach used for integrating latest pushed changes of Asciidoctor gem into Asciidoctor Java Integration, works so well because it has detected a problem. The bad news are that I don't know exactly where is the problem, and before starting with git bisect I would like to know if you have a quick answer why.

Basically you can see the problem here:

11 days ago I run it the last time a full integration between gem and java with latest Asciidoctor gem (https://travis-ci.org/asciidoctor/asciidoctor-java-integration/builds/8251591), today I have run it again, but without any modification on Java code (see git hash tag), but the build has failed with the error:

org.jruby.exceptions.RaiseException: (LoadError) no such file to load -- asciidoctor
        at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1054)
        at RUBY.require(jar:file:/opt/repo/org/jruby/jruby-complete/1.7.4/jruby-complete-1.7.4.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/custom_require.rb:36)

So it seems like asciidoctor module is no longer available but at the same time this seems impossible, so any idea of which issue could be modified Asciidoctor gem in the way that cannot be loaded by JRuby?

If there is nothing, then I will start with git bisect.