Skip to content

Proper JRuby at runtime requirement#578

Merged
chadlwilson merged 1 commit intomasterfrom
kares-patch-1
Oct 14, 2025
Merged

Proper JRuby at runtime requirement#578
chadlwilson merged 1 commit intomasterfrom
kares-patch-1

Conversation

@kares
Copy link
Member

@kares kares commented Oct 14, 2025

This will effectively declare the proper JRuby version at runtime.

Building and running Ruby version might be completely different with Warbler, that's why b7b47b7 won't have the proper effect.

This will effectively declare the proper JRuby version at runtime.

Building and running Ruby version might be completely different with Warbler, that's why b7b47b7 won't have the proper effect.
@chadlwilson
Copy link
Contributor

I believe if you use different build and run versions of JRuby with Warbler these days you can end up with all sorts of bundler issues because the bundler versions that come with the various JRuby versions change on patch releases, and by default everyone's lockfiles have BUNDLED WITH in them (since bundler seems to be more aggressive at including this by default now) - so bundler ends up trying to restart itself in a new process via ENV['RUBY'] and then failing since that doesn't work on JRuby.

(e.g jruby 9.4 went through 3 different default bundler versions, 2.3.25 --> 2.3.26 --> 2.6.3)

However, there are many combinations of approaches with warbler, so not sure if that's true for all of them.

@chadlwilson chadlwilson merged commit d438bb2 into master Oct 14, 2025
10 checks passed
@chadlwilson chadlwilson deleted the kares-patch-1 branch October 14, 2025 09:47
@kares kares mentioned this pull request Oct 14, 2025
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

Successfully merging this pull request may close these issues.

2 participants