rake tasks are broken with latest rubygem versions (v. 2 or later)

[famished-tiger]

Method ForkedCucumberRunner#gem_available? caused an error in rake with
the message 'undefined method available? for Gem:Module'.
This occurred when rubygems could not find a gem, then the method falled back to a legacy call to the Gem::Module#available? that doesn't exist anymore in rubygems 2 and
above. The fix consists in avoiding to call the obsolete method when Rubygems has version 2 or above.

[mattwynne]

Thanks!

If you could help us to investigate why the build has failed on JRuby we'll be able to get this released quicker.

[famished-tiger]

Hi Matt,

When updating my own project macro4cuke yesterday evening, I also got Travis CI failures with two RVM environments:

jruby-19mode and ruby-head
The build went perfect for:
Ruby 1.9.2, 1.9.3, 2.0.0 and jruby-head.

Looking at the Travis CI log, I discovered that my cucumber fork had exactly the same error message:

$ gem --version
2.0.3
$ bundle install
ERROR: Gem bundler is not installed, run gem install bundler first.
The command "bundle install" failed. Retrying, 2 of 3.

and so on...
The failing environments have in common the use the latest rubygems version (2.0.3).  What is perplexing, I tested locally the fork with rubygems 2.0.3 without a problem.
At first, I suspect that the failures are caused by some improper config of the RVM environments at the Travis CI side (well this is how I can interpret the above log excerpt: the build fails even before cucumber started).

Kind regards,
Famished Tiger
(always in quest of thought food)

---

From: Matt Wynne notifications@github.com
To: cucumber/cucumber cucumber@noreply.github.com
Cc: famished-tiger famished.tiger@yahoo.com
Sent: Wednesday, June 19, 2013 11:09 AM
Subject: Re: [cucumber] rake tasks are broken with latest rubygem versions (v. 2 or later) (#491)

Thanks!
If you could help us to investigate why the build has failed on JRuby we'll be able to get this released quicker.
—
Reply to this email directly or view it on GitHub.

[famished-tiger]

The JRuby build in Travis CI is now passing while code wasn't changed.
This points to a temporary issue in the config of the JRuby build environment in Travis CI, not the Cucumber code.

[famished-tiger]

Disregard what I just said:
-The JRuby build went over the point where it stopped previously. But it failed while executing the feature file:

cucumber -p jruby features/docs/getting_started.feature:6 # Scenario: Run Cucumber in an empty directory

[mattwynne]

Dupe of #448

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.