Tyler Jennings wrote: > I'm having a problem with rails 2.3.2, engines, and eager loading. > There is a default set of eager_load_paths (the usual suspects under > app/) that will be greedily required by rails at boot time when you're > running with threadsafe! on, and of course you can append your own > custom paths. However, so far as I can tell, engines are never > eagerly loaded and therefore unavailable when the system is running in > threadsafe! mode.
> Your help is greatly appreciated, Ping core about it? =r -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
