This seems fine - thought it should be clear that for general plugin usage in "normal" rails development, the plugin_migration generator is the tool to use.
Directly running migrations from within plugins (via such rake tasks) should only be required when you need multiple migration streams (i.e. when building plugins for an externally-maintained application, like Mephisto). Go ahead and commit :) James On 19/02/2008, Sven Fuchs <[EMAIL PROTECTED]> wrote: > I'd like to add these rake tasks to Engines: http://pastie.caboo.se/154218 > > The background is that we could use something like this for Mephisto > to give users a way to avoid version number clashes with their plugin > migrations and future Mephisto migrations. Also I've seen situations > where script/generated plugin_migrations causes version number clashes > when two developers worked on different plugins and then tried to > check their generated migrations in to the repository. > > The rake tasks above generally avoid these issues. They certainly > aren't suited for every situation (that's why the plugin_migration > generator exists), but I believe they work fine for quite some others. > > > > -- > sven fuchs [EMAIL PROTECTED] > artweb design http://www.artweb-design.de > grünberger 65 + 49 (0) 30 - 47 98 69 96 (phone) > d-10245 berlin + 49 (0) 171 - 35 20 38 4 (mobile) > > > > _______________________________________________ > Engine-Developers mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org > -- * J * ~ _______________________________________________ Engine-Developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
