> In general a task that installs a gem shouldn't need to rely on much.
The gem tasks depend on the initializer firing up because they allow
things like config.gem 'rspec' in test.rb but not development.rb. Can
you reproduce this in an empty test app?
This problem is NOT reproducible in a simple test app:
echo 'MY_CONSTANT = true' > config/initializers/test2_1_1.rb
puts "MY_CONSTANT exists"
add to end of Rails::Initializer.run do |config| block:
config.gem "rspec-rails", :lib => "spec"
$ rake gems:install
$ rake gems:unpack
Unpacked gem: '/Users/stephen/dev/rails/test2_1_1/vendor/gems/rspec-rails-1.1.8'
So unless I'm misreading this, it seems we're requiring application.rb
before we try to run the gem installs, but we *haven't* fired the
Is it perhaps caused by one of your plugins (rspec f.ex) requiring
There's something different between the apps -- -- I will investigate further -- if I find anything further that might indicate a rails problem I'll update this thread.
Thanks for your response.