-
Notifications
You must be signed in to change notification settings - Fork 172
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
Compatibility with Java 9 #515
Comments
When converting your docs with the asciidoctor-maven-plugin or asciidoctor-gradle-plugin you should be able to manually upgrade the dependency on org.jruby:jruby-complete 9.1.x.y (I think the latest version is even 9.1.5.0) But we will probably not upgrade the version of JRuby in asciidoctorJ 1.5.x to 9.x.y.z as this breaks compatibility with Java 6 and I am not in favor of doing such a drastic change of the requirements in a minor release. The next "major" version 1.6.0 will be based on JRuby 9.x.y.z instead. So to sum it up: you are free to use another, newer version of JRuby which hopefully works with Java9. I personally didn't find the time yet to test it out on Java9 but hope to find that time soon. Another note: if you already tried it out yourself with Java9 it would be great if you could attach any error logs etc to this issue, this helps a lot. |
Hi @robertpanzer ! Thanks for the quick reply. I'd be happy to use version 1.6.0, I wasn't implying this upgrade should happen in any specific version. When I override the JRuby version of the asciidoctor-maven-plugin our documentation seems to build fine indeed; thanks for the hint! |
@Sanne Are you using Java-based extensions at all, or are you just using AsciidoctorJ by way of the Maven plugin? If the latter, you shouldn't really be nervous about which version of AsciidoctorJ you are using since in that use case, it's just a thin wrapper to call the same Asciidoctor core under the covers. When it really matters which AsciidoctorJ you are using is when you are using the Java API. And if you are using the Java API, I recommend for projects who can to use AsciidoctorJ 1.6.0 alpha.
We probably should to be testing AsciidoctorJ against the latest JRuby release in CI. |
Interesting, thanks @mojavelinux ! We don't use extensions in Hibernate ORM, Hibernate OGM, Hibernate Search. We use them for the Bean Validation specification. I'll update the first group so we'll see how it does if someone notices any rendering problem. |
If you need assistance getting asciidoctorj running on JRuby 9.1.3.0+, let us know. Don't assume it's your fault if something fails. We probably would accept patches to get JRuby 1.7.x running on Java 9, but we still intend to EOL JRuby 1.7.x by year's end (jruby/jruby#4112). |
Thanks @headius! |
Fails on Apache Camel using java 9 build 156 even when upgrading to jruby 9.1.7.0. Workaround is to set
Though the issue seems to come more from JRuby than from asciidoctor.
|
A new JRuby is in the works right now. Is this something we need to report? cc: @headius |
I try AsciidoctorJ with Java 9. The core works well, but I get a SSL exception while generating PDF with asciidoctorj-pdf.
|
That version of AsciidoctorJ-PDF shouldn't be compatible with JRuby 1.7.xx. |
@robertpanzer AsciidoctorJ 1.5.4 still uses JRuby 1.7.21 in its dependency graph. Which AsciidoctorJ and AsciidoctorJ-Pdf dependency combination should I use? I tried several combinations but neither of them works so far. |
Thanks for testing Java 9, @rahmanusta. I know this is something the OpenJDK team is looking feedback on, so your feedback is very valuable to them as well as the AsciidoctorJ project. |
works well for me with Java 10 (on Windows at least). Would be great if this gets resolved to avoid having to fiddle around with versions. |
This fixes a problem when building on OpenJDK 11. See also asciidoctor/asciidoctorj#515.
This fixes a problem when building on OpenJDK 11. See also asciidoctor/asciidoctorj#515.
Pretty sure this should be ok with a more recent JRuby, if that hasn't happened already. |
Oh yes, we also have the CI running with Java 11 now. |
asciidoctorj is currently not going to work on Java 9 as this would require to update JRuby to at least version 9.1.3.0 according to @headius :
I'd highly appreciate some help to get this upgrade done!
I was going to try it myself but I found #362 which made me understand it's not a good task for a beginner (I'm not familiar with the project.. heck I don't even know Ruby!).
In Hibernate we've almost the full build working on Java 9 now, it's just missing a couple patches yet in Javassist but then the documentation still fails to build. We use asciidoctorj for all docs of course ;-)
The text was updated successfully, but these errors were encountered: