-
-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with launching sub-jruby #4030
Comments
The files that I'm running — # foo.rb
require 'rake'
require 'rake/file_utils'
include FileUtils
puts "inside foo.rb"
ruby 'bar.rb', 'foo=bar' # bar.rb
puts "inside bar.rb #{ARGV.inspect}" |
The problem seems to be how Rake, in the meanwhile uses
This is clearly a problem because the arguments really need to be I'm not sure what the fix should be. Is there a workaround that someone know that'll allow me to use the jruby-complete jar to create a subshell? |
I thought there were one or two tests with jruby-complete.jar and rake. I am bit confused about your example and the gradle classpath popping up from somewhere. anyways IMO we should fix this, i.e. let |
If it helps avoid confusion — the gradle from the stacktrace is because I'm running jruby from the gradle cache, so the path shows up in the stacktrace. This is how it looks like when running with jruby-complete from my downloads folder —
|
Environment
Provide at least:
jruby -v
) and command line (flags, JRUBY_OPTS, etc)jruby 1.7.25 (1.9.3p551) 2016-04-13 867cb81 on Java HotSpot(TM) 64-Bit Server VM 1.7.0_79-b15 +jit [darwin-x86_64]
also reproducible with
jruby 9.1.2.0 (2.3.0) 2016-05-26 7357c8f Java HotSpot(TM) 64-Bit Server VM 24.79-b02 on 1.7.0_79-b15 +jit [darwin-x86_64]
uname -a
)Darwin ketanpkr.local 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64 i386 MacBookPro11,4 Darwin
Expected Behavior
With the attached code, I'm able to run fine with MRI. Tested on
1.9.3p551
,2.0.0p648
,2.1.5p273
2.2.4p230
The output I see is —
Actual Behavior
The actual behavior with both jruby 1.7.25 and 9.1.2.0 is —
The text was updated successfully, but these errors were encountered: