On Oct 13, 2010, at 6:30 AM, Matt Davies wrote:
> I've found a solution.
>> I upgraded rspec-rails to 1.3.3 in my gemfile, which in turn downgraded
> rspec from 2.0 to 1.3.1 in the gem list. This configuration now works
> ok. God knows what was happening there.
rspec-rails-1.3.2 depends on rspec >= 1.3.0, so if you have rspec-2 installed, it tries to load it.
rspec-rails-1.3.3 depends on rspec-1.3.1 explicitly.
Make sense?
Cheers,
David