Join GitHub today
Rails new failed with JRuby on Windows 7 #1171
I am pretty sure something doesn't work with Rails on JRuby 1.7, since Rails 4 worked fine with RBI-s on the same PC, I am ready to say the issue lies somewhere in JRuby. I am surprised though. I'd think this would have come up earlier.
I upgraded to JRuby 1.7.6, I had 1.6.4 and updated first to see if that would work OK. No. So I am saying the issue has been around for some little time.
Here's the relevant Windows CMD console output.
Gives the following stack dump:
I am guessing that something in Rails 4.0 invokes something JRuby wasn't comfortable with. It looks to me like the problem is in the loader (from a require command).
Oh the environment is Windows 7 SP1, 64-bit, all windows updates applied at time of writing; Java 1.7.0 u45.
I kept the console output for Ruby 2 & Rails (worked) as well as JRuby & Rails (failed) but there's no way to attach files to the bug report, it seems. I can email them if that could help.
Behavior confirmed. However bundle install is getting called from parent process is passing illegal environment values. If we manually set ENV with these values we get an error, so somehow this is not supposed to provide these when child processes are being invoked (or they are getting swallowed).
I'm sorry but I can't understand that response. Which ENV variable is being passed? It would be helpful to describe a possible workaround.
From the stack trace, I can confirm that "Z:" is the disk drive of the current path (pwd) when the 'Rails New' command was run. I would expect that to belong somewhere as a valid part of the environment for a 'new' command.