Hi all, The two key features missing from the 'engines' support in Rails 2.3 are migrations and public assets; the latter isn't too hard to handle for plugins themselves, but migrations are a bit trickier, so I'm really keen to get something into core that is simple and consistent.
Luca Guidi has done some great work around this, but unfortunately, it's a tricky problem. I've used the discussion here (http:// interblah.net/plugin-migrations) to clarify my own thoughts, and hopefully others will find it useful. The two key problems are maintaining the timeline (so that rollback is consistent), and detecting which migrations have already been run. I've attached what I believe to be the simplest, least-intrusive implementation I can think of to the ticket - http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2058-rake-tasks-for-run-engine-migrations#ticket-2058-22 Please take a look, and let me know what you think. James --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
