On 17 Apr 2009, at 15:03, Tom Stuart wrote:
the bad commit is http://github.com/dchelimsky/rspec-rails/commit/c9abdccedee97217f28e07ec824bb12cda1c9173
I don't understand what's happening to rspec.rake in this commit. In particular, how is the "require 'spec/rake/spectask'" line meant to succeed once the $LOAD_PATH.unshift has been removed? On my system it's this code that adds vendor/plugins/rspec/lib to the load path, so removing it causes the require to fail.
If this was just a mistake then perhaps the attached patch is the appropriate fix. However, I'm confused why nobody else has seen this problem -- am I the last man on earth to be using RSpec as plugins instead of gems?
Cheers, -Tom
0001-Fix-rspec.rake-to-require-Rails-environment-so-that.patch
Description: Binary data
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
