-
-
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
JRuby 1.7.5 doesn't handle wildcards during gem install anymore (on Windows) #1093
Comments
jruby 1.7.5 updated to rubygems 2.1.5. Maybe this is a change in behavior of rubygems? Does this work on MRI with rubygems 2.1.5? |
Updated to rubygems 2.1.9 and the problem persists. |
Closing this issue since it appears to be a bug with rubygems. I will open an issue on that project. I went back to JRuby 1.7.4 which includes rubygems 1.8.24. I could use wildcards. Updating to rubygems 2.1.9 broke that behavior so looks like rubygems is the culprit. |
Per @headius request, reopening this issue. Problem was resolved by a patch to rubygems (see rubygems/rubygems#697) but for whatever reason MRI did not suffer from the same problem. Therefore, it is probably doing some kind of wildcard expansion on Windows that JRuby should mimic. |
This second problem mentioned in this issue is because we are not properly handling quotes or wildcards like a normal windows application would. MRI does this processing. We have a more modern issue open on this (I promise) but I am not going to hunt for it. |
When running JRuby 1.7.4 on Windows, one can move into a directory that contains a gem file (e.g. somegem-1.0.0.gem) and install it without using the entire name:
or
Under 1.7.5, these commands now return:
ERROR: Could not find a valid gem '*.gem' (>= 0) in any repository.
To work, the entire name must now be handed off to the gem command:
The text was updated successfully, but these errors were encountered: