Updating to Ruby 2.0 broke my asset pipeline

Question

I installed Ruby 2.0 to try it out with my Rails 3.1.12 app.

All of the same gems are able to be installed with Ruby 2.0.0. Gemfile.lock doesn't even change.

But now when I load pages, I get javascript errors that jQuery isn't defined. And none of the files that my manifest says to include show up, in development. I tried pushing to a staging env, to see if they'd be included during precompile, but they weren't.

Here's production, still with Ruby 1.9.2, here's staging with Ruby 2.0.0, and here's the full diff of what I changed between the two.

wtf?

Answer 1

Rails 3.1.x does not work with Ruby >= 2.0.

If you want to use the wonderfully speedy Ruby >= 2.0, upgrade to Rails >= 3.2.13. (It will be worth the effort.)