Forum: Ruby on Rails Fwd: Engines, plugins, migrations.. and moaning

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
6cf8286fcab5843f468d62f5e6fb22de?d=identicon&s=25 Henry Turner (Guest)
on 2007-01-20 14:21
(Received via mailing list)

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.. ?

This topic is locked and can not be replied to.