On 10/3/07, Michael Koziarski <[EMAIL PROTECTED]> wrote: > > > > Are we going to "fix" this in Rails 2.0 Initializer (ie. make it not > whine > > about missing ARes)? > > This seems reasonable, it will at least stop hurting people when we > next release from trunk.
The biggest problem is the misleading error message and stack trace. I've investigated, and it turns out Mongrel swallows LoadErrors raised in Rails::Initializer. (Don't ask me why.) After it swallows the error, something happens that pushes the Rails 1.2.3 gem into load paths, "commands/servers/mongrel.rb" gets re-loaded from the wrong place and the whole thing crashes miserably. Koz, please see my patch: http://dev.rubyonrails.org/attachment/ticket/9743/require-frameworks.diff It doesn't make Rails tolerate LoadErrors in require_frameworks. Without ARes, starting Mongrel will still fail, but at least with this patch users will get the proper error message and stack trace about not being able to load ARes. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
