Add support for jruby 10.1 #3003

Activity

1. larouxn

   added

   feature requestFeature requestsFeature requests

   on Jul 7, 2026
2. hiSandog commented on Jul 11, 2026

   

   hiSandog

   on Jul 11, 2026

   More actions

   The pry-nav failure may be better treated as a development-tooling compatibility issue rather than blocking runtime support for JRuby 10.1. It could be useful to run the main test suite in a minimal dependency group first, then test console/debug dependencies separately. That split would clarify whether any production code changes are actually required.

   👍React with 👍1Reacted by Nicholas La Roux
3. larouxn commented on Jul 11, 2026

   

   larouxn

   on Jul 11, 2026

   Author

   More actions

   What do we think about doing this as a way to unblock CI from running against jruby 10.1?

   diff --git a/elasticsearch-api/Gemfile b/elasticsearch-api/Gemfile
   index fd00bfdf..4a9ee6fc 100644
   --- a/elasticsearch-api/Gemfile
   +++ b/elasticsearch-api/Gemfile
   @@ -28,7 +28,7 @@ group :development do
      gem 'rspec'
      gem 'rspec_junit_formatter'
      if defined?(JRUBY_VERSION)
   -    gem 'pry-nav'
   +    gem 'pry-nav' if Gem::Version.new(JRUBY_VERSION) < Gem::Version.new('10.1')
      else
        gem 'debug'
      end
   diff --git a/elasticsearch-api/spec/spec_helper.rb b/elasticsearch-api/spec/spec_helper.rb
   index aa79707a..aa0df0dd 100644
   --- a/elasticsearch-api/spec/spec_helper.rb
   +++ b/elasticsearch-api/spec/spec_helper.rb
   @@ -22,7 +22,12 @@ if ENV['COVERAGE']
    end
    
    if defined?(JRUBY_VERSION)
   -  require 'pry-nav'
   +  if Gem::Version.new(JRUBY_VERSION) < Gem::Version.new('10.1')
   +    begin
   +      require 'pry-nav'
   +    rescue LoadError
   +    end
   +  end
    else
      require 'debug'
    end