Thanks for the note on testing. I think what we have decided to is develop the plugin in a stand alone rails app that has it's own engine. Then as as deployment process, copy out all the appropriate files from the rails app down into the engine/plugin and let that be the master plugin that we deploy out to our other apps.
Hopefully, tis will allow us to have good abstraction while at the same time keep the engine lightweight. -J Justin Blake wrote: > On 3/15/07, James Ho <[EMAIL PROTECTED]> wrote: >> Given our development model, if things need to be added to the engine >> such as models, migrations and controllers what is the best way to do >> this? Since a plugin does not have it's own generators it would be quite >> a maintenance nightmare, not to mention destroying the elegance and >> abstraction of engines, to generate them in the top level rails apps and >> keep copying everything down to the engine. > > This might not be the solution you're looking for, but I simply don't > use generators when adding things to the engine. As a side effect I > found it forced me to learn the rails structure a bit better :) > >> What do we do about unit testing the engine by itself? > > I'm assuming you're running the latest engines plugin since you're > using rails 1.2. So if you put your engine tests in > vendor/plugins/engine_name/test they can be run with rake test:plugins > PLUGIN=engine_name > > Justin > _______________________________________________ > engine-developers mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org _______________________________________________ engine-developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
