Forum: Rails Engines Migrations with Engines 1.2?

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.
58a68672882676f6bdf817b3c8ff3880?d=identicon&s=25 Tony Arcieri (Guest)
on 2007-01-26 02:09
(Received via mailing list)
So do I have to install plugin_migrations to run my migrations now?  I
installed the plugin_dependencies, loaded_plugins, and plugin_migrations
plugins (uggggh) and rake db:migrate:plugins gibs with:

rake aborted!
can't convert Array into String

757deb60e31c0541c58cd1243e3aebcb?d=identicon&s=25 Martijn van Leeuwen - MVLWebdesign (Guest)
on 2007-01-26 09:08
(Received via mailing list)
Run a plugin_migration yes. And than rake db:migrate. Works fine here.
05d703f649ef1d07e78d7b479fb4c4ac?d=identicon&s=25 James Adam (Guest)
on 2007-01-26 09:29
(Received via mailing list)
No - you don't need to install any other plugins. Run

  script/generate plugin_migration [PLUGIN=name]

To create migrations in your application for your installed plugins.
This is different from pluginaweek's "plugin_migrations" plugin - it's
a generator that comes with the engines plugin.
58a68672882676f6bdf817b3c8ff3880?d=identicon&s=25 Tony Arcieri (Guest)
on 2007-09-25 22:41
(Received via mailing list)
Well, never mind... adding PLUGIN=my_engine solved the problem.

Is this the "recommended" way of doing migrations now?

- Tony
This topic is locked and can not be replied to.