Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README instructions for WildFly don't work #647

Open
heruan opened this issue May 10, 2018 · 3 comments
Open

README instructions for WildFly don't work #647

heruan opened this issue May 10, 2018 · 3 comments

Comments

@heruan
Copy link

heruan commented May 10, 2018

I've followed the README instruction on how to deal with WildFly (version 12 in my case), but I still get this exception:

org.jruby.exceptions.RaiseException: (LoadError) no such file to load -- asciidoctor
	at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1040)
	at RUBY.require(/opt/wildfly/modules/org/asciidoctor/main/jruby-complete-1.7.26.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:54)
	at RUBY.(root)(<script>:12)

This is using the versions specified in the README, i.e.

  • asciidoctorj: 1.5.6
  • jcommander: 1.35 (seems very old)
  • jruby-complete: 1.7.26

Strangely enough, if I downgrade jruby-complete to version 1.7.21 the exception disappears and all seems to work. But I see AsciidoctorJ 1.5.6 does depend on the versions in the README, so I doubt my workaround being safe for production.

Why that exception gets thrown? I guess something changed between JRuby 1.7.21 and 1.7.22 is causing this, but I have no clue how to find it out.

@abelsromero
Copy link
Member

I'd recommend upgrading to jruby 9.1.8.0. Support for 1.7.x will deprecated with the next release.
Does this also fail with 9.1.8.0 or higher?

@heruan
Copy link
Author

heruan commented May 10, 2018

I didn't try to change the major version to avoid breaking changes, but indeed with the latest 9.1.17.0 it seems to work! Maybe then it's just a matter of updating the docs.

P.S. Also tried to update JCommander to 1.72 and I didn't experience any issue.

@abelsromero
Copy link
Member

I didn't try to change the major version to avoid breaking changes, but indeed with the latest 9.1.17.0 it seems to work! Maybe then it's just a matter of updating the docs.

jRuby is the runtime that runs the underlying Ruby Asciidoctor core. It is a non-written goal to keep compatibility with a wide range of versions, but it's always advisable to use the most recent one. Specially if you want to add extensions and converters to the mix.

P.S. Also tried to update JCommander to 1.72 and I didn't experience any issue.

JCommander is for the cli interface. @robertpanzer do we really need to keep it in the Wildfly docs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants