RSpec and Rake

Guys,

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.

I’ve downgraded rake to 0.8.7. Are there any ‘side-effects’ that may
impact
the operation of rspec?

Cheers,
Jason

On May 28, 2011, at 7:12 AM, Jason N. wrote:

Guys,

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?

Nope.

Cheers,
David

On Sat, May 28, 2011 at 8:12 AM, Jason N. [email protected] wrote:

Guys,

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.

I’ve downgraded rake to 0.8.7. Are there any ‘side-effects’ that may impact
the operation of rspec?

Not that I know of. Removing 0.9.0 and making sure your rails project is
using 0.8.7 again is all you need to do. It happened to me and this is
what
I did - it’s all working fine.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs