On Mon, Nov 24, 2008 at 6:33 PM, Matt Jones <[EMAIL PROTECTED]> wrote: > > 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.
This is a chicken and egg scenario, no wonder it is such hot topic. Good point, didn't consider that since I was hunting the bug in extreme anger. > FWIW, this problem goes away on edge - > http://github.com/rails/rails/commit/a026b4c983681b71d876ea37958c3e5bc605acac > avoids preloading ApplicationController, and thus solves this. (I > tested it...) Nice, will have a look too. > What's the error about the specifications? $ rake gems (in /home/kenneth/work/tmp/rails-broken-gems-example) - [I] settingslogic rake aborted! You have a nil object when you didn't expect it! The error occurred while evaluating nil.dependencies vendor/rails/railties/lib/rails/gem_dependency.rb:77:in `dependencies' all_dependencies = specification.dependencies.map do |dependency| GemDependency.new(dependency.name, :requirement => dependency.version_requirements) end Thanks for digging into this with me. Best -- Kenneth Kalmer [EMAIL PROTECTED] http://opensourcery.co.za --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
