Hi, If I''m not mistaken, placing controllers, views and especially migrations in plain plugins doesn''t work. It seems the only way to do this is with engines.. Third party applications, with third party repositories, cry out to be kept separate from the main app. Once you merge foreign code with your own keeping up on fixes can be an unnecessary nightmare. (A classic app in this category is forum software where integration is barely more than translating user models.) So.. why do people moan about engines? Is there some magical solution/solutions out there we should be using as a replacement? And if not, can anyone invisage the future?.. I can''t see engines style functionality getting into the core but I can''t see engines going away for a while.. ? cheers -henry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---