David Chelimsky wrote in post #967419: > This is a regression that was introduced by an enhancement in > rspec-mocks-2.2. It has been reported, identified, and fixed, but not > yet released: > > https://github.com/rspec/rspec-rails/issues/closed#issue/266 > > I'll try to get an rspec-rails-2.2.2 release out this weekend with > this fix. In the mean time, you can point your Gemfile to the branch > on github and get the fix right now: > > gem "rspec-rails", :git => "git://github.com/rspec/rspec-rails", > :branch => "2-2-maintenance" > > HTH, > David
It appears that the fix you mention is in master not 2-2-maintenance. Due to RSpec 2.3 dependancies I've added the following to my Gemfile gem 'rspec', :git => 'git://github.com/rspec/rspec.git' gem 'rspec-expectations', :git => 'git://github.com/rspec/rspec-expectations.git' gem 'rspec-core', :git => 'git://github.com/rspec/rspec-core.git' gem 'rspec-mocks', :git => 'git://github.com/rspec/rspec-mocks.git' gem 'rspec-rails', :git => 'git://github.com/rspec/rspec-rails' Unfortunately, the same error persists. :( -- Posted via http://www.ruby-forum.com/. _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
