Am 12.12.2007 um 17:55 schrieb Sven Fuchs: > it works for me. Whoops, sorry.
It works for me in an outdated version that I'm still using for a client ... but it doesn't seem to work with the current trunk (which is, IMO, correct). Am 12.12.2007 um 18:51 schrieb James Adam: > I'm not sure that Rails has ever allowed automatic reloading of code > from plugins in development - can anyone confirm this? Yes, I think this is true. They once tried to change it, but ran into issues with plugins that rely on their classes not being auto-reloaded and thus invented Dependencies.load_once_paths. See Rick's post on this: http://weblog.techno-weenie.net/2007/1/26/understanding-the-rails-plugin-initialization-process I strongly believe that this is the wrong approach to it though, as it leads to all kinds of weird side-effects. A better approach to it would be to whitelist those plugins that don't want to be auto- reloaded but auto-reload everything else. (Actually there's even a config.load_once_paths feature that would allow to do this.) -- sven fuchs [EMAIL PROTECTED] artweb design http://www.artweb-design.de grünberger 65 + 49 (0) 30 - 47 98 69 96 (phone) d-10245 berlin + 49 (0) 171 - 35 20 38 4 (mobile) _______________________________________________ Engine-Developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
