In version 1.5.4.1 , "(LoadError) no such file to load -- asciidoctor"

See original GitHub issue

When I upgraded my maven dependencies from v1.5.4 to 1.5.4.1 , i started getting this error “(LoadError) no such file to load – asciidoctor”.

I am not sure, whether I did something wrong. But when I rolled back to prev version, my code started working fine. org.jruby.exceptions.RaiseException: (LoadError) no such file to load -- asciidoctor at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1040) at RUBY.require(/C:/jframeworks/projects/snapcx/src/main/webapp/WEB-INF/lib/jruby-complete-1.7.25.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:54) at RUBY.(root)(<script>:9)

Issue Analytics

State:
Created 7 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

abelsromerocommented, Jan 4, 2017

I am assuming, this will be still valid defect for this project? so that it can be fixed as part of next minor release.?

This is not properly an AsciidoctorJ issue, but I admit is kind-of grey area. Is a known issue that some envrionments with custom Classloaders cause issues with jRuby. That makes that locating the gems embbeded in the jars as well as some extensions or converters sometimes fail. Each case is special and most of the cases the solution revolves around choosing the right jRuby version, or take care of how the app is packaged. Keep in mind that the use of jRuby 1.7.x versions is to keep compatibility with Java 6 for AsciidoctorJ 1.5.x. AsciidoctorJ 1.6.0 will use jRuby 9k by default at the cost of not supporting Java 6, so many scenarios will be fixed. We try our best to provide support and alternatives every time someone rises an issue, but is not something we can fix from our side.

In fact, the ability to customize the jRuby dependency is something we support and in some cases encourage. To mention some cases: · Maven plugin allows to change the jruby version and in the examples repo you’ll see different versions depending on the case https://github.com/asciidoctor/asciidoctor-maven-examples · The Asciidoctor Gradle plugin also offer ways to do it, even if not so explicitly. · SpringBoot gradle plugin also acknowledges the special needs of AsciidoctorJ and jRuby packaging and adds the requiresUnpack option to keep those jars from the rest of dependencies. · AsciidoctorJ defines specific instructions to deploy in WildFly https://github.com/asciidoctor/asciidoctorj#installation …and so others…

I don’t have permissions on this repo so, this issue will remain open unless you close it. But I don’t think any action will be derived from it.

0reactions

mojavelinuxcommented, Apr 22, 2017

We’ll call this a support case. I’ll close it since it provides information about how to address the problem. If someone has an idea for a code change, feel free to propose it.