Migrations concensus?

rogerdpack · September 21, 2018, 6:06am

It appears from
http://rails-engines.org/news/2009/02/02/engines-in-rails-2-3/

that migrations and copying public assets are no longer supported.

However, from

lazyatom/engines/blob/bc5cd970e048dfe5e0e8c06ccf4969bd0d1299be/tasks/engines.rake

# This code lets us redefine existing Rake tasks, which is extremely
# handy for modifying existing Rails rake tasks.
# Credit for the original snippet of code goes to Jeremy Kemper
# http://pastie.caboo.se/9620
unless Rake::TaskManager.methods.include?('redefine_task')
  module Rake
    module TaskManager
      def redefine_task(task_class, args, &block)
        task_name, arg_names, deps = resolve_args([args])
        task_name = task_class.scope_name(@scope, task_name)
        deps = [deps] unless deps.respond_to?(:to_ary)
        deps = deps.collect {|d| d.to_s }
        task = @tasks[task_name.to_s] = task_class.new(task_name, self)
        task.application = self
        task.add_description(@last_description)
        @last_description = nil
        task.enhance(deps, &block)
        task
      end

This file has been truncated. show original

it appears that migrations are still supported via a rake task (for non
time stamped migrations), and from

http://groups.google.com/group/rubyonrails-core/browse_thread/thread/fbc79b21b0ddc3ed/9d6fc87d110061d7?lnk=gst&q=engines#9d6fc87d110061d7

that it still copies in public assets. Anyone have any insights on this
one?

Was there ever any concensus on these?
Thanks!
-r

rogerdpack · September 22, 2018, 6:53am

On 9 Oct 2009, at 13:40, Roger P. wrote:

It appears from
http://rails-engines.org/news/2009/02/02/engines-in-rails-2-3/

that migrations and copying public assets are no longer supported.

Of the aspects of ‘engines’ that Rails 2.3 integrated, migrations and
public asset copying were not included

that it still copies in public assets. Anyone have any insights on
this
one?

This is still in the plugin, which can be used along-side Rails 2.3

Was there ever any concensus on these?
Thanks!

Not really. Despite my RailsConf talk essentially being a plea that we
try and figure this stuff out together, participation really dropped
off to zero, except for the routing ticket.

James

rogerdpack · September 22, 2018, 6:54am

This is still in the plugin, which can be used along-side Rails 2.3

Nice.

Not really. Despite my RailsConf talk essentially being a plea that we try
and figure this stuff out together, participation really dropped off to
zero, except for the routing ticket.

I thought that routing was also dropped on the floor–something of a
“if they want their own order to create routes in, they should tweak
it all themselves” or something?
Thanks for engines. Works pretty good.
-r

rogerdpack · September 22, 2018, 6:54am

On 12 Oct 2009, at 15:22, Roger P. wrote:

Not really. Despite my RailsConf talk essentially being a plea that
we try
and figure this stuff out together, participation really dropped
off to
zero, except for the routing ticket.

I thought that routing was also dropped on the floor–something of a
“if they want their own order to create routes in, they should tweak
it all themselves” or something?

I believe I had a fairly iron-clad case that plugin routing without
precidence control was only useful in the simplest of cases, but it’s
hard to convince a busy entrepreneur of much over IM, and the ‘Russian
Dolls’ vaporware (no offence, Yehuda) distracted from my own pleas, I
think.

Only time will tell what the future brings…

All the best,

James

rogerdpack · September 22, 2018, 6:54am

Not really. Despite my RailsConf talk essentially being a plea that
we try and figure this stuff out together, participation really
dropped off to zero, except for the routing ticket.

James

I’m sorry I never came to the party with my ideas. I’m still using
rails 2.1 for production, so it doesn’t affect me, but it might
eventually

Kind regards,
Samuel