I don't know if this is feasable in your case, but I'd be tempted to start a brand new project in Rails 3, try to get the Gemfile correct and work out problems there, generate scaffolding for all your controllers, etc, from scratch, then use a diff tool to move your existing code into the new files.
On Fri, Mar 25, 2011 at 7:03 AM, Matt Jones <[email protected]> wrote: > > > On Mar 24, 5:48 pm, "sol.manager" <[email protected]> wrote: >> We have an app that is at Rails 2.1.0 and our web developer has let us >> know going to 3.0 will cost some money. I have embarked on a personal >> project to see what is involved in getting from 2.1.0 to 3.0. I have >> the app up and running on 2.2.2 (with some fun along the way) and now >> tried to get 2.3.4 and see a gem_dependency conflict type issue. > > You don't need to hit all the intermediate releases, but there are > some bumpy spots in the gem dependency manager in 2.x. What error > message are you getting? > > --Matt Jones -- 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.
