The common way to supply app specific configuration information for plugins appears to be defining constants at the top-level of one of the environment files. Even with config/initializers in Rails 2.0 this feels a bit clunky. Also, as the application initializers are loaded after plugins this might be just too late.
I have no very clear idea of or concrete suggestion for what I'd like to have. Maybe a two phase process, where, first, only a config object is loaded for a plugin which can be customized in initializers and second the plugin proper is loaded with that config. -- Or maybe this is just overkill for a non-problem.
Michael
