> Make it print the message to STDERR instead of raising an error? Plus > add a > blurb like "You can ignore this warning if you didn't intend to run > specs" > > Aslak
I like that too, +1 for me. > Obviously if your production code is explicitly calling rspec, you've > got bigger problems. As Stephen said, it's because rspec.rake located under the lib folder is trying to load rspec (gem or plugin) without looking at the rails environment. -- Posted via http://www.ruby-forum.com/. _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
