On 9 Oct 2009, at 13:40, Roger Pack 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
However, from
http://github.com/lazyatom/engines/blob/bc5cd970e048dfe5e0e8c06ccf4969bd0d1299be/tasks/engines.rake
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?
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
_______________________________________________
Engine-Users mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
