On May 28, 2011, at 7:12 AM, Jason N. wrote:
Just upgraded to rspec / rspec-rails 2.6 today and noticed that it pulled in
rake 0.9.0 which was causing the rails 3.0.7 tasks to blowup.
RSpec doesn’t have a runtime dependency on rake, so it was not RSpec
that caused this. It’s more likely that another gem in your Gemfile
declares a runtime dependency on rake >= 0.8 (or similar), in which case
Bundler tells Rubygems to install the newer rake.
To avoid this, just specify “gem ‘rake’, ‘0.8.7’” in your Gemfile.
There is one caveat: we had an issue with spork over the past few days
where installing it pulled rake 0.9 in the “install native extensions”
cycle. This has been fixed in spork, with 0.8.5 and 0.9.0.rc8 releases,
but other libs could do this, in which case you have no way to stop it.
I’ve downgraded rake to 0.8.7. Are there any ‘side-effects’ that may impact the
operation of rspec?