The problem with loading initializers is that they are likely to try
to use the configured gems
(ie, to set options, etc.). So loading them is going to cause more
problems than it solves.
FWIW, this problem goes away on edge -
http://github.com/rails/rails/commit/a026b4c983681b71d876ea37958c3e5bc605acac
avoids preloading ApplicationController, and thus solves this. (I
tested it...)
What's the error about the specifications?
--Matt
On Nov 24, 2008, at 11:00 AM, Kenneth Kalmer wrote:
>
> On Mon, Nov 24, 2008 at 5:05 PM, Kenneth Kalmer
> <[EMAIL PROTECTED]> wrote:
>> On Mon, Nov 24, 2008 at 2:38 PM, Kenneth Kalmer>
>>
>> In a nutshell, it boils down to the one-line patch below:
>>
>> --- a/vendor/rails/railties/lib/initializer.rb
>> +++ b/vendor/rails/railties/lib/initializer.rb
>> @@ -284,7 +284,7 @@ module Rails
>> def check_gem_dependencies
>> unloaded_gems = @configuration.gems.reject { |g| g.loaded? }
>> if unloaded_gems.size > 0
>> - @gems_dependencies_loaded = false
>> + @gems_dependencies_loaded = false || $rails_gem_installer
>> # don't print if the gems rake tasks are being run
>> unless $rails_gem_installer
>> abort <<-end_error
>>
>> Any feedback would be appreciated, including pointers to the correct
>> Lighthouse tickets for making my case.
>
> Seems I was in a too big a hurry, this does solve the initial issue
> but creates a new one upon running 'rake gems', which now complains
> about the gem specifications...
>
> I'll investigate and report my findings.
>
> Best
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
