The biggest problematic change in Edge Rails that will affect engines
is the new plugin loading mechanism, which will conflict with the way
that the engines plugin (see a post on this thread by Rhett for the
specific changeset).

Because we don't develop against Edge at work (in general), we've not
needed to deal with this problem yet. It requires some thought because
the direction core has taken the plugin loading mechanism doesn't suit
my needs. In a nutshell, do provide a new "PluginLoader" class, that
class needs to be available on the load path before the initializer
starts up. That's going to mean either repackaging the engines plugin
as a gem and adding "gem 'engines'" to the top of environment.rb, or
some other dastardly hack. I'm still undecided. Any thoughts?

It's worth noting that until there's a pressing need here for the
plugin to work with Edge rails, it won't get much attention, but if
any of you have the need, please do discuss possible approaches, and
submit patches! http://dev.rails-engines.org/ is your playground!

Cheers,

James

On 4/30/07, David Smalley <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> We're using engines heavily in our current app - problem is that we've
> seen the lovely patch DHH just committed to edge rails to allow easy
> namespacing of routes (
> http://railstips.org/2007/4/28/namespaces-added-to-routes ). We'd really
> like to move to edge to take advantage of this but we're so heavily
> dependant on the current release of engines that we can't afford to
> break that.
>
> So - anyone know of any issues with edge rails and the current stable
> release of engines? Would we have to move over to an edge version of
> engines as well?
>
> Cheers,
>
> David
> _______________________________________________
> engine-users mailing list
> [email protected]
> http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
>


-- 
* J *
  ~
_______________________________________________
engine-users mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org

Reply via email to