Upgrading Rails 3.0 Beta4 to Rails 3.0 Release Candidate

by woody2shoes on July 27, 2010

This video goes over some issues that popped up while upgrading a Rails 3 application to the Release Candidate

This video goes over some issues that popped up while upgrading a Rails 3 application to the Release Candidate.
Download 131 MB
Download (iphone & ipod) 11.7 MB

Tagged as: bundler, cucumber, rails, rails3, ruby, tutorial

  • John

    Maybe the routes deprecation error is caused by the block variable 'map' that is passed? It's not needed anymore..

  • http://twitter.com/billsaysthis billsaysthis

    For the DSL deprecation warning just take the |map| off the end of the start of the routing block:

    YourApp::Application.routes.draw do

    instead of

    YourApp::Application.routes.draw do |map|

  • Andrius Chamentauskas

    I really didn't check new Rails routing thoroughly, but I noticed you have “routes.draw do |map|”. If I had to guess, I'd guess the “|map|” part is the one giving you deprecation warnings.

  • woody2shoes

    Thanks for the help. Feedback like this helps everyone and it's why I released a video without the answer in it.

  • Aaron Tinio

    Running `rake rails:update` helped me zero in on the cause of the deprecation warning. You may also want to run `bundle update` (replaces lock and unlock) to update your gems.

  • Aaron Tinio

    In your Rakefile, Rails::Application needs to be changed to YourAppName::Application

Previous post:

Next post: