`bundle exec <cmd>` gives "command not found" on JRuby+Windows

[eregon]

Environment Information

Provide at least:

• JRuby 9.2.9.0
• Windows

See https://github.com/rubygems/bundler/issues/7602 and ruby/setup-ruby#18 (comment)

It's unclear if this is a Bundler bug or JRuby bug, but given that it works on MRI on Windows, and I it seems unlikely Bundler has code specific to MRI for bundle exec, I think it would be a JRuby bug.

Note that if there is any argument, the bug does not happen:

$ bundle exec rake
bundler: command not found: rake
Install missing gem executables with `bundle install`

$ bundle exec rake default
OK

Therefore a workaround is to replace bundle exec rake with bundle exec rake default but it's obviously just a workaround.

[slonopotamus]

This was fixed on Bundler side: ruby/rubygems#3256 (comment)

[eregon]

Let's close then, thanks for checking.
@slonopotamus Could you file a separate issue for the warning on this tracker?

[eregon]

This seems to be an issue again:
https://github.com/eregon/childprocess/runs/2869731199?check_suite_focus=true

bundler: command not found: rake
Install missing gem executables with `bundle install`

That's JRuby 9.2.19.0 and Bundler 2.2.20.

[headius]

Unable to reproduce with a clean download of JRuby 9.2.19.0, Bundler 2.2.21, Rake 12.3.3:

C:\jruby-9.2.19.0\tmp>jruby -S bundle install
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies...
Using rake 12.3.3
Using bundler 2.2.21
Bundle complete! 1 Gemfile dependency, 2 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.

C:\jruby-9.2.19.0\tmp>jruby -S bundle exec rake -T
rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
C:/jruby-9.2.19.0/bin/bundle:23:in `<main>'
(See full trace by running task with --trace)

[headius]

Since I cannot reproduce this with the standard JRuby 9.2.19.0 zip download, it seems the problem must lie somewhere else.

If you are able to reproduce in isolation from setup-ruby please open a new issue, since this one was resolved by a Bundler update. Any future issue found to be JRuby's fault should be a new bug report.

[eregon]

jruby -S bundle exec rake -T

The bug only happens with no arguments at all, as mentioned in the description, could you try literally bundle exec rake with jruby in PATH to see if that reproduces?

[headius]

C:\jruby-9.2.19.0\tmp>jruby -S bundle exec rake
rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
C:/jruby-9.2.19.0/bin/bundle:23:in `<main>'
(See full trace by running task with --trace)

[headius]

Also

C:\jruby-9.2.19.0\tmp>bundle exec rake
rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
C:\jruby-9.2.19.0\bin\bundle:23:in `<main>'
(See full trace by running task with --trace)