Koz (or others), Has this issue has been addressed, and if so, in which commit?
-Chris On Nov 7, 3:07 am, "Michael Koziarski" <[EMAIL PROTECTED]> wrote: > > Solution: I moved the `require_frameworks`call to the start of > > `Initializer#process`. Of course, `silence_warnings` is not defined by that > > time so I defined a no-op method on Initializer with the same name. > > This seems like a reasonable change, there doesn't seem to be anything > important that it will be being moved in front of. > > > I probably could have just said `config.cache_classes = false` instead. > > Rails then assumes this is a development environment and doesn't preload. > > I'm happy with config.cache_classes = false as a work around if it > fixes the issue you had. It's a little dirty but shouldn't have any > performance impact as you're not calling reload!. Failing that, we > could add a config.preload_classes value to cover this case. > > -- > Cheers > > Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
