[rspec-users] Rake tasks getting in the way of edge (uses gem instead)

[David Richards]

What I've done with this is to just uninstall the gem and commit to  
working off of the plugins completely.  I've found that with gems in  
general, I try to keep them local to the project I'm on, almost as if  
they were a plugin.  I move them to my project's lib (gem unpack) so  
that I've got explicit control over versions and dependencies and I  
can very easily encapsulate my work domain when I go to deploy an  
app.  Committing to the rspec plugins gives me the same features for  
free.

Hope this helps,

David


On Sep 4, 2007, at 1:55 PM, Pat Maddox wrote:

> So I'd been running gem releases of rspec for the past several months,
> and I installed edge rspec so that I can use Story Runner.
>
> I'm running into a problem because I've got a couple rake tasks that
> reference "spec/rake/raketask".  If I try to run "rake spec" then it
> pulls in the gem version instead of the plugin version.  rake blows up
> saying that the versions are incompatible...RSpec is at 1.0.8 and
> rspec_on_rails is at r2507.
>
> If I remove those rake tasks then it runs fine.  So it just seems that
> when rake starts up, it loads all the available task files, which
> includes a reference to require rspec stuff.  Since the plugins
> haven't been loaded yet it gets the gem version.
>
> afaik the solution is to build a new gem.  However I don't want to
> have to tell my team members to update their gem every single day.
> Also I think including rspec in vendor/plugins is supposed to obviate
> that anyway, but this is probably just some path loading stuff.
>
> Anyone else run into this?  How do you handle it?
>
> Pat
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users