First commit anything you''ve done and tag it with some note about the
working version of Rails that supports that code. Next:
rake rails:freeze:edge
(if it''s really old, then just rake freeze edge)
rake rails:freeze:edge
Yes, I really meant to type that twice. The first time you update
most of the core but don''t pull down ActiveResource, the next time,
the new Rake task is on your local computer so ActiveResource is added.
Then
rake rails:update
rake
And see what tests are broken.
On Jul 11, 2007, at 8:41 PM, Sean Colquhoun wrote:
>
> Does anybody have any tips on upgrading an older rails project to a
> newer version of rails? I have a project that is still calling up
> WeBrick in dev mode and I''d like to bring it up to date. Short of
> creating a whole new rails project and copy-pasting, is there a quick
> and easy way to upgrade?
>
> Thanks!
>
> --
> Posted via http://www.ruby-forum.com/.
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---