Known third-party issues

[eregon]

• JRuby 9.1 + Bundler 2: JRuby 9.1.17.0 cannot run bundle install #108
  • Bundler 1 is used instead on JRuby 9.1 automatically in ruby/setup-ruby (Ruby 2.3 is EOL and uses a very old RubyGems)

---

Fixed upstream, simply use a newer Bundler release:

• Ruby 2.3 + Bundler 2: LoadError: cannot load such file -- bundler/gem_tasks, incorrect entry for Bundler in $LOAD_PATH rubygems/rubygems#3570
  • Bundler 1 is used instead on Ruby 2.3 automatically in ruby/setup-ruby (Ruby 2.3 is EOL and uses a very old RubyGems)
  • Remove bundler enforcement on ruby 2.3 #146
• JRuby + Bundler 2.1.4 + Windows + bundle exec rake: bundle exec <cmd> gives "command not found" on JRuby+Windows rubygems/rubygems#3256 and JRuby on Windows: "bundler: command not found: rake" #18, fixed in Bundler 2.2.0
• JRuby + Bundler 2.2.0 + Windows: Bundler 2.2.0 fails on JRuby 9.2 on Windows rubygems/rubygems#4129, fixed in Bundler 2.2.2
• Bundler 2.2.0 + Gemfile.lock created with older version: Bundler does not find platform specific gem rubygems/rubygems#4123, fixed in Bundler 2.2.1

[deivid-rodriguez]

For completeness, the fix for rubygems/rubygems#3570 was released with bundler 2.2.0.rc.1, and regarding #108 we never got a report about it 🤷.

[eregon]

Regarding #108, I was hoping @JonRowe would report it to Bundler or JRuby in #108 (comment), but I probably wasn't clear enough. @JonRowe Could you do that?

Maybe I should write this in the issue template: only file a bug here after you've filed a bug upstream, but it's hard to make a general rule that's still correct in all cases.

[deivid-rodriguez]

Yeah, no problem at all! It might be a bug in jruby, but since bundler 1 works, I guess we could probably do something to workaround it. I think it could be due to us stopping using Dir.chdir there and instead the :chdir parameter of Kernel.system and family.

If that was the issue, we could easily workaround it by using git -C which I'm sure has been supported for many many years.

[eregon]

Marking this issue as closed as there is outstanding 3rd party issue, that is not already worked around.