Hi Hans - I have recently completed an upgrade of 3 applications (with 2 more to go) with more than a dozen plugins from Rails 2.3.5 to Rails 3.0.6.
My process was to do not only upgrade each app but to convert each plugin into a rails engine-gem. I made a Rails3 branch of each of our repo's. For each app and plugin I ran: rails new . Where conflicts exist I either merged the changes manually - in some cases like environment.rb you may have things going in 2 or 3 different places. I started with the engines which are lowest on the build order and moved up until I had the applications running. We are also upgrading to rspec 2.5, with upgrades to shoulda and factory_girl - rspec is SO different that we have are still working through the upgrades to get all the testing working again. We chose to get the applications working again first just to verify our approach and engine design and well for a bit we couldnt even run rake tasks. In our case - to make matters more complicated - many of our engines have models and migrations - and we have a separate schema namespace for each engine - this required alot of custom extensions to the PostgreSQLAdapters and other ActiveRecord classes - these had some fixes and as well the rspec.rake tasks and others had to be rewritten. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
