I've seen something similar, where application.rb gets required when I'm trying to run rake db:migrate.
I guess there's some plugin we're all using. On Nov 25, 1:26 pm, Chris Cruft <[EMAIL PROTECTED]> wrote: > I've seen this behavior as well: my initializers were not being run > during a gem install, but application.rb was being required. Inside > initializer.rb, the "gems_dependencies_loaded" test was not being met > and so the "load_application_initializers" method had no effect. > > In my case, the initializers were defining some constants needed for > application.rb. I resorted to installing the gem manually. > > -Chris > > On Oct 10, 6:00 am, "Michael Koziarski" <[EMAIL PROTECTED]> wrote: > > > > 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? > > > 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 > > initializers yet? > > > Is it perhaps caused by one of your plugins (rspec f.ex) requiring > > application.rb? > > -- > > Cheers > > > Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
