We announced this on Twitter, but it’s important enough to put here for posterity.
FYI, since 3.2 rubygems.org is the default Gemfile source, this means you need to have jruby-openssl installed before "rails new".— JRuby Dev Team (@jruby) January 31, 2012
To clarify, the following is put in
Gemfile for new Rails 3.2 apps:
This means that the
jruby-openssl gem must be installed before you
can generate a new Rails application.
An alternative is to run
rails new --skip-bundle, ensure
jruby-openssl is installed, and then run
bundle install inside
your new application.
We’re looking at options for incorporating more of jruby-openssl into
JRuby proper without importing the export-controlled crypto bits
(which is the reason we don’t currently ship
JRuby). If you’re interested, join us.