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.

Sign up for GitHub

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

Jump to bottom

can install jruby-openssl gems but not using it - always using default gem #3000

Closed
mkristian opened this issue May 28, 2015 · 2 comments
Closed

can install jruby-openssl gems but not using it - always using default gem #3000

mkristian opened this issue May 28, 2015 · 2 comments
Assignees
@mkristian
Labels
JRuby 1.7.x JRuby 9000 stdlib
Milestone
Invalid or Duplicate

Comments

@mkristian
Copy link
Member

setup

GEM_PATH=tmp GEM_HOME=$GEM_PATH java -jar jruby-complete-1.7.19.jar -S gem install jruby-openssl --version 0.9.6

with jruby-1.7.19 the installed gem gets activated

GEM_PATH=tmp GEM_HOME=$GEM_PATH java -jar jruby-complete-1.7.19.jar
#<Gem::Specification:0x7d0 jruby-openssl-0.9.6-java>

with jruby-1.7.20 the default gem from jruby gets activated

GEM_PATH=tmp GEM_HOME=$GEM_PATH java -jar jruby-complete-1.7.20.jar
#<Gem::Specification:0x7d0 jruby-openssl-0.9.7-java>

expected to use jruby-openssl-0.9.6-java. same results with using jruby-openssl-0.9.8.dev: jruby-1.7.20 ignores the installed gem but jruby-1.7.19 uses the installed gem.
@mkristian mkristian self-assigned this May 28, 2015
@mkristian mkristian added this to the JRuby 1.7.21 milestone May 28, 2015
@mkristian
Copy link
Member Author

jruby-9k.pre2 behaves like 1.7.20

@mkristian mkristian changed the title can install jruby-openssl gems, always using default gem can install jruby-openssl gems but not using it - always using default gem Jun 15, 2015
@mkristian
Copy link
Member Author

@kares
upgrade works as expected.

downgrade is working via bundler or gem 'jruby-openssl', '0.9.6' since rubygems just looks at all the installed gems (including the default gems) and picks the latest version. but prereleased gems are not picked. this behavior changed with some rubygems upgrades.

so it is a feature not a bug. closing for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mkristian mkristian

Labels
JRuby 1.7.x JRuby 9000 stdlib
Projects
None yet
Milestone
Invalid or Duplicate
Development

No branches or pull requests
1 participant
@mkristian