Messing around with the plugin loading mechanism (as I love to do), I
stumbled on a $LOAD_PATH oddity and I was wondering if I'm missing the
reasoning behind it. At the moment, plugin lib directories are added
to the $LOAD_PATH by two independent mechanisms:
* Rails::Initializer#load_plugins adds them when the plugin is loaded
* Rails::Initializer::Configuration#default_load_paths includes
them by default
This behaviour seems broken in the light of the config.plugins; if I
have chosen to control the plugins I need to load, other plugin lib
directories simply shouldn't be available to Rails.
If there's a reason for this, I'd love to know; alternatively, there's
a tiny patch here: http://dev.rubyonrails.org/ticket/6842
Also, while I've got your attention, I noticed a while back that Koz
suggested that plugin load order could be controlled by
"The recent addition of config.plugins will let you specify which
plugins to load, and which order to load them in."
This, alas, isn't the case. Is there any support for having Rails
respect the order that plugins are specified in on config.plugins?
Rather than being anything approaching "plugin dependencies" (spit,
gag, splutter), this just adds a bit more meaning to an existing