I run into the same issue last week just 2 hours before the meetup @ Blazing Cloud... Sorry, I didn't email about it. I thought it was my rvm.
So, in the Spanish version, which is exactly the same as the English Version --cucumber in spanish-- rake wasn't working at all.
What I did was:
I remove rake - 0.9.1 and modified Gem file
rvm use @global && gem uninstall rake -v 0.9.1
Gemfile
gem 'rake', '0.8.7' (added to the script that generates Gemfile)
When rake 0.9.2 was released I tried with it (and removed from Gemfile) and "rake cucumber" worked super.
Right now my environment
Rake 0.9.2, Rails 3.0.7 and gem 1.8.5 works perfectly fine now. Thanks Alex for the DLS warning fix.
In my case, rake 0.9.0 and 0.9.1 exposed other gems issues. So I had to add gem rake '0.8.7' to Gemfiles to my others Rails 3.0.x projects.
Bundler reported that rake-0.8.7 was being installed, said nothing about 0.9 and gem list rake showed me 3 versions installed. I ended up running my test with "bundle exec" which is the right thing to do (according to the experts ;-) but I keep forgetting. I removed rake 0.9.1 once I read about the fixes and everything went back to normal.
I think we should use "bundle exec" and tell the students (and myself!!) to do it too to make sure that we are pulling the right gems and add it to the wiki.
Quoting from the bundler documentation:
In some cases, running executables without bundle exec may work, if the
executable happens to be installed in your system and does not pull in
any gems that conflict with your bundle. However, this is unreliable and
is the source of considerable pain. Even if it looks like it works, it
may not work in the future or on another machine.
On Wed, Jun 8, 2011 at 12:41 PM, Ginny Hendry
<ginny...@gmail.com> wrote:
OK, I'll test with 3.0.8 and gem 1.8.5 to see how it goes.
Thanks.
-Ginny
On Wed, Jun 8, 2011 at 2:27 PM, Alex Chaffee
<al...@stinky.com> wrote:
On Wed, Jun 8, 2011 at 11:40 AM, Ginny Hendry
<ginny...@gmail.com> wrote:
In our June 4 workshop, we found that the install fest instructions caused Bundler to install rake 0.9.1 which was a mess.
Yeah. Ugh. I had to teach a Ruby class week before last, and my students came away with the impression that Ruby is an unstable platform.
It caused many errors including some warnings about DSLs
That's fixed by my Rakefile patch, and hopefully also by Rails 3.0.8.
and other messages that didn't sound like they had anything to do with rake but went away when we got rake 0.8.7 installed.
Sadly, as you saw, there is a strong force pulling rake towards the latest version. Even if you install rake 0.8.7 in some places, your PATH or your rvm global gemset might retain the latest version and mess everything up.
We had to uninstall rake 0.9.1, add a line in Gemfile to specify rake 0.8.7, then do "bundle exec rake", then "bundle install" and then check to make sure rake 0.9.1 wasn't there. It took several tries on some machines to get this to work.
I am planning to update the install instructions this week to fix this and several other problems we found.
Fortunately, I think rake 0.9.2 and gem 1.8.5 fixes (or nearly fixes) everything (knock wood). Actually, let me knock wood outside parentheses too: KNOCK WOOD. Please don't change the install instructions until you've gone through the same annoying aggravating process with those versions.
--
--
You received this message because you are subscribed to the Google Groups "RailsBridge Workshops" group.
To post to this group, send email to
railsbridg...@googlegroups.com.
To unsubscribe from this group, send email to
railsbridge-work...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/railsbridge-workshops?hl=en.
--
Carmencita