Skip to content
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

JRuby 1.7.11 not working in Windows 7 Enterprise version #2555

Closed
ambirag opened this issue Feb 3, 2015 · 2 comments
Closed

JRuby 1.7.11 not working in Windows 7 Enterprise version #2555

ambirag opened this issue Feb 3, 2015 · 2 comments

Comments

@ambirag
Copy link

ambirag commented Feb 3, 2015

JRuby 1.7.11
Window 7 Enterprise
Service Pack 1
64 bit OS
When JRuby bin is set to the PATH and any command that starts with jruby -S fails with the error given below. This is severely blocking us from moving our cucumber/watir-webdriver automation to JRuby.
This is perfectly working fine on Mac, Win2k3, Win2k8.

D:\dev\trunk\ui\test\cucumber>jruby -S gem install bundler -f -v 1.3.5
NameError: undefined local variable or method `??' for main:Object
(root) at D:/dev/trunk/buildtools/jruby/1.7.11/lib/ruby/shared/rubygems/specification.rb:1
require at org/jruby/RubyKernel.java:1085
(root) at D:/dev/trunk/buildtools/jruby/1.7.11/lib/ruby/shared/rubygems.rb:1
Gem at D:/dev/trunk/buildtools/jruby/1.7.11/lib/ruby/shared/rubygems.rb:1161
require at org/jruby/RubyKernel.java:1085
(root) at D:/dev/trunk/buildtools/jruby/1.7.11/lib/ruby/shared/rubygems.rb:114
load at org/jruby/RubyKernel.java:1101
(root) at file:/D:/dev/trunk/buildtools/jruby/1.7.11/lib/jruby.jar!/jruby/kernel19/rubygems.rb:1

@headius
Copy link
Member

headius commented Feb 24, 2015

Can you test with a more recent JRuby version? We periodically verify JRuby on Windows and simple things like gem install should definitely be working.

@enebo enebo added this to the Invalid or Duplicate milestone May 16, 2017
@enebo
Copy link
Member

enebo commented May 16, 2017

I used all of 1.7.x on 64 bit win 7 for a majority of my testing. I am guessing this was an env issue of some kind. Since 1.7.x is EOL I am closing this.

@enebo enebo closed this as completed May 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants