I had a similar problem and I finally traced it down to the way I named and loaded my models. I don't know if this applies to your situation it might give you a clue.
I had a model Spec::AppComponent which is used in a platform system we were building. When that model was referenced in the initialzers it would cause the errors described above to occur. When I renamed the model to AppComponent the issue disappeared. My guess, is that because I have rspec as a plugin, that the reference to the Spec module is somehow causing rspec to load. Hope this helps. On Aug 6, 3:35 pm, Jim Cropcho <[EMAIL PROTECTED]> wrote: > anybody have any ideas about this? i still haven't got it. > > On Aug 5, 3:56 pm, Jim Cropcho <[EMAIL PROTECTED]> wrote: > > > holy crap, I am about to give you guys a headache, I think (thanks for > > all the help so far). > > > so, my gem list (after our fix): > > > config.gem 'haml',:source => "http://gems.github.com"; > > config.gem 'mime-types' , :lib => 'mime/types' > > config.gem 'json' > > > removed rspec, and no more "alias" or test/unit problems for script/ > > console. but check this out: > > > $ rake db:migrate > > (in /XXX/XX/XXX) > > ** Invoke db:migrate (first_time) > > ** Invoke environment (first_time) > > ** Execute environment > > ** Execute db:migrate > > ** Invoke db:schema:dump (first_time) > > ** Invoke environment > > ** Execute db:schema:dump > > Loaded suite /usr/bin/rake > > Started > > > Finished in 0.000228 seconds. > > > 0 tests, 0 assertions, 0 failures, 0 errors > > > yea, that's right. now i'm getting it for all my rake tasks. add rspec > > back to environment.rb and they go away for rake and come back for > > console. > > > frustration... > > > btw, i haven't added rspec to /environments/test.rb or anything like > > that yet, so that doesn't play a role here. > > > need more info? please ask. > > > let's figure this out! > > > On Aug 5, 3:11 pm, RSL <[EMAIL PROTECTED]> wrote: > > > > i use vendor/plugins/rspec and rspec-rails [cause i use edge a decent > > > amount] so it's never been an issue. i've had a few vendor/gems before > > > but they all just worked with config.gem out of the box. [thank you > > > rails team!] what's the specifics on the gem that's not loading right? > > > > RSL --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
