No it is not. I managed to get the issue reproduced in a very tiny
application using Rails 2.2.2.
The code is available at
git://github.com/kennethkalmer/rails-broken-gems-example.git and shows
exactly how to simulate the breakage mentioned by Steven. Please
review the README file
(http://github.com/kennethkalmer/rails-broken-gems-example/tree/master)
for a complete breakdown of the issue and how to fix it.
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...
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...)
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.
$ 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
all_dependencies = specification.dependencies.map do |dependency|
GemDependency.new(dependency.name, :requirement =>
dependency.version_requirements)
end
all_dependencies = specification.dependencies.map do |dependency|
GemDependency.new(dependency.name, :requirement =>
dependency.version_requirements)
end
Oops - this bit actually is a bug. It’s a short patch; I’ll put it up on Lighthouse tonight with
Not that I'm currently aware off. I'll continue trying to find some
fringe cases and in those cases address the issue more clearly than I
did this one (and without anger).