Forum: Rails Engines development Additional plugin migrations rake tasks

402602a60e500e85f2f5dc1ff3648ecb?d=identicon&s=25 Sven Fuchs (Guest)
on 2008-02-19 13:11
(Received via mailing list)
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      svenfuchs@artweb-design.de
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)
05d703f649ef1d07e78d7b479fb4c4ac?d=identicon&s=25 James Adam (Guest)
on 2008-02-19 15:33
(Received via mailing list)
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
402602a60e500e85f2f5dc1ff3648ecb?d=identicon&s=25 Sven Fuchs (Guest)
on 2008-02-19 16:59
(Received via mailing list)
Am 19.02.2008 um 15:33 schrieb James Adam:
> 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).

Yep, sure.

> Go ahead and commit :)


Just wanted to do so. But I'm confused about the repository layout.
Would that change go to

http://svn.rails-engines.org/engines/trunk/

or

http://svn.rails-engines.org/plugins/engines/

or both?


--
sven fuchs      svenfuchs@artweb-design.de
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)
05d703f649ef1d07e78d7b479fb4c4ac?d=identicon&s=25 James Adam (Guest)
on 2008-02-19 18:35
(Received via mailing list)
On 19/02/2008, Sven Fuchs <svenfuchs@artweb-design.de> wrote:
> Just wanted to do so. But I'm confused about the repository layout.
> Would that change go to
>
> http://svn.rails-engines.org/engines/trunk/

http://svn.rails-engines.org/README should be useful, but in general:

/plugins/engines only exists for the 'script/plugin' script, which was
(until recently, I believe) deeply confused by trunk/branches/tags as
the endpoints of an SVN url

/engines is the part of the repository dedicated to the engines plugin
itself

/engines/trunk is the current development 'branch'

/engines/tags/rel_1.2.1 is a tag of development that's stable (and
will never be changed - use this for externals should you wish)

> or
> http://svn.rails-engines.org/plugins/engines/

this is basically a special tag for 'script/plugin'. I'll update it
when we're comfortable that we have a version that's stable and
working for the current release of Rails. Which could be now, given
the lack of noise on the issue tracker :)

James
402602a60e500e85f2f5dc1ff3648ecb?d=identicon&s=25 Sven Fuchs (Guest)
on 2008-02-20 19:41
(Received via mailing list)
Hi James,

thanks for the guidance :)

I've now commited to engines/trunk:

http://svn.rails-engines.org/engines/trunk/tasks/e...

Thanks!


Am 19.02.2008 um 18:35 schrieb James Adam:

> the endpoints of an SVN url
>> http://svn.rails-engines.org/plugins/engines/
>  ~
> _______________________________________________
> Engine-Developers mailing list
> Engine-Developers@lists.rails-engines.org
> http://lists.rails-engines.org/listinfo.cgi/engine...

--
sven fuchs      svenfuchs@artweb-design.de
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)
This topic is locked and can not be replied to.