0.9.0.rc3 being loaded

[Jo Liss]

Hey Tim, hey list,

Here's a minor problem I'm having with Spork 0.9.0.rc4:

My Gemfile(.lock) says:

Gemfile: gem 'spork', '~> 0.9.0.rc4'
Gemfile.lock: spork (0.9.0.rc4)
Gemfile.lock: spork (~> 0.9.0.rc4)

But as long as I have /var/lib/gems/1.9.1/gems/spork-0.9.0.rc3 (left
over from before the upgrade) on my disk, I get the following error:

$ bundle exec spork
/var/lib/gems/1.9.1/gems/spork-0.9.0.rc3/lib/spork/test_framework/cucumber.rb:2:
warning: already initialized constant DEFAULT_PORT
/var/lib/gems/1.9.1/gems/spork-0.9.0.rc3/lib/spork/test_framework/cucumber.rb:3:
warning: already initialized constant HELPER_FILE
/var/lib/gems/1.9.1/gems/spork-0.9.0.rc3/lib/spork/test_framework/rspec.rb:2:
warning: already initialized constant DEFAULT_PORT
/var/lib/gems/1.9.1/gems/spork-0.9.0.rc3/lib/spork/test_framework/rspec.rb:3:
warning: already initialized constant HELPER_FILE
Using RSpec
Preloading Rails environment
Loading Spork.prefork block...
Spork is ready and listening on 8989!

Only after I delete the spork-0.9.0.rc3 directory do the error messages go away.

Any idea what's going on? Let me know if there's any other info I can provide.

Jo

--
Jo Liss
http://opinionated-programmer.com/

[Tim Harper]

Hmm, there's some ruby-gems auto-detection code that might be
over-stepping the bounds of Bundler... which may be an issue with
Bundler or may be an issue with the auto-detection code. It basically
allows other gems to define integration hooks for spork, so rather
than storing cucumber-specific code in spork to integrate it with
cucumber, the code is stored in cucumber to integrate with spork, and
spork can pick up on it and automatically use it.