Include a backwards-compatability task library with the old names that just delegates to the new modularized ones? Might be overkill if it's not going to be a serious problem but it's relatively easy to do.
On 2/27/06, David Heinemeier Hansson <[EMAIL PROTECTED]> wrote: > So Rake 0.7 allows for namespaces in actions. It's mighty nice. rake > db:schema:import and rake db:schema:export whips the llama's ass on > db_schema_import/export. It makes it much to organize tasks. Yay, yay. > > But how does this relate to backwards compatibility? What would happen > if the next release changed all the tasks over to be namespaced? Who > and want would break? I'm coming up short with ideas on where it would > be a problem, but I'd like to hear if others have some dependencies on > the specific rake names. > -- > David Heinemeier Hansson > http://www.loudthinking.com -- Broadcasting Brain > http://www.basecamphq.com -- Online project management > http://www.backpackit.com -- Personal information manager > http://www.rubyonrails.com -- Web-application framework > _______________________________________________ > Rails-core mailing list > [email protected] > http://lists.rubyonrails.org/mailman/listinfo/rails-core > _______________________________________________ Rails-core mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-core
