-
Notifications
You must be signed in to change notification settings - Fork 31
LoadError: OpenSSL::SSL requires the jruby-openssl gem #2
Comments
Try adding to your Gemfile
If that fixes, I'll add to the README as a requirement. Don't think we can add jruby only dependencies to a gem. |
Sadly this did not work. Thanks for the response though! |
:( I'll try harder on the weekend. |
Having the same issue while trying to play with Jetpack -- created a new Rails app for testing, added the jetpack gem to Gemfile, and configured jetpack.yml. Executed
to the Gemfile ... still no joy. |
Oh so I think what you have to do is run bundler using JRuby at least once so that java becomes listed as a platform in your |
@sconover and I just encountered this problem internally. For us it was because the Gemfile specified a source of "https://rubygems.org" and as soon as we just used plain http it worked like a champ. |
@cchandler that did it for me too |
@cchandler Thanks! |
@cchandler +1. http worked for me too. |
Hi, I'm getting this issue also :) I think I know the issue, but I'm still a bit confused. I'm using rvm with jruby 1.7.4, but the gem only loads jetpack when using MRI. So I should create a new rvm layout using MRI and use that soley for the purposes of building? I guess people use this for production builds only and not for development b/c of the constant switching of rubies? |
@cchandler what do you mean 'just used plain http', my gemfile.lock has remote: https://rubygems.org/, what should I be doing to use http? |
top of Gemfile source 'http://rubygems.org' On Sun, Jun 9, 2013 at 1:56 PM, Salman Ahmed notifications@github.comwrote:
|
thanks that worked. |
I already have source 'http://rubygems.org' instead of 'https' in Gemfile, but I still get the same error |
+1 |
Created a new rails app
rails new jetpack
. Added the jetpack gem andconfig/jetpack.yml
to the new rails application. Ranbundle exec jetpack .
inside the rails app.Resulted in the following:
I'm also using rbenv, not sure if this is causing issues.
The text was updated successfully, but these errors were encountered: