<nirvdrum>
So, I took that as some new requirement I overlooked. Changing to "require_java 15" fails. I didn't look too much, but I think the version string format inspection doesn't work quite right. Removing the line entirely got 9.2.15.0 installed.
<nirvdrum>
This check seems unnecessary to me. I can't imagine anyone installing JRuby would be unaware they need a JVM set up. And even then, it'd fail when trying to invoke it, which ought to be fairly obvious.
<headius[m]>
Yeah file a bug with ruby-build I guess
<nirvdrum>
Cool. Thanks for the clarification.
<headius[m]>
Perhaps they do this check because they need to run jruby for part of the installation
<headius[m]>
So not having Java at all would fail halfway through
<nirvdrum>
I think it just unpacks the tarball.
<nirvdrum>
Heh. Booting this old JRuby + TorqueBox project is a pain in the neck. There were core library and even syntax changes reflected in 9k. 1.7.x doesn't work with newer Java releases.
<nirvdrum>
I should probably bite the bullet and track down a Java 7 build.
<nirvdrum>
It looks like the CA support in Java 8 doesn't handle the rubygems.org SSL certificate.
<headius[m]>
There are 7 builds from a number of sources
<headius[m]>
Wish we could have kept TB going but the devs moved to other projects. To much for just two of us to handle
<nirvdrum>
Well, booting a project that hasn't been booted in six years can't be a terribly common use case. I guess I had hoped that being Java-based, this would have gone smoother. I'm a bit constrained by this crazy old version of sidekiq-pro I have cached because I can't download any other versions and I must have downloaded that early into my work on JRuby+Truffle, since I had set it up with JRuby 9.0.5.0. But, I can't get that to communicate with
<nirvdrum>
rubygems.org due to the aforementioned SSL issue. Updating to work with JRuby 9.2 is just requiring a bunch of changes, including one to the internals of TorqueBox.
<nirvdrum>
And I don't know when it happened, but at some point Bundler did something different with its dependency resolution, so the TorqueBox gems don't resolve correctly. It sees "3.1.0" and "3.1.0-java" as different, but that's how the graph resolves. I had to roll back to Bundler 1.10 to get past that or keep manually modifying the Gemfile.lock.
<headius[m]>
Hmm that is odd. What exactly is the ssl issue?
<nirvdrum>
I haven't dug too deeply into it, but I see this when running "rbenv install 9.0.5.0":
<nirvdrum>
ERROR: Could not find a valid gem 'jruby-launcher' (>= 0), here is why: