I was happily cuking along, until a new developer also tried to run the
cucumber stuff, and then, since they’ve got a shiny new install without
any gems installed, it all fails miserably for them.
The first link is the only thing I’m able to find that is relevant to
this. It must be a new-ish glitch
I hit the same error. I tried adding:
install rubygems-update
update --system
The update --system command gave me an error (dont have my other laptop
with the error with me). I tried doing the same thing in my local jruby
installation on this laptop:
gem install rubygems-update (updates to 1.8.8)
gem update --systems
and then gem install cuke4duke (installed 0.4.4)
and it worked fine. However my maven installation wont get cuke4duke to
install.
I hit the same error. I tried adding:
install rubygems-update
update --system
The update --system command gave me an error (dont have my other laptop
with the error with me).
So looking into the source code for the cuke4duke maven plugin, it uses
an internal GemTask object to do gem tasks. So update --system wouldn’t
work anyway, because there’s no gem command to update, and it appears
it’s not being used anyhow.
I tried doing the same thing in my local jruby
installation on this laptop:
gem install rubygems-update (updates to 1.8.8)
gem update --systems
Yep, that would work just fine, because it’d be updating/installing an
actual gem command file that gets used instead.
I hit the same error. I tried adding:
install rubygems-update
update --system
The update --system command gave me an error (dont have my other laptop
with the error with me).
So looking into the source code for the cuke4duke maven plugin, it uses
an internal GemTask object to do gem tasks. So update --system wouldn’t
work anyway, because there’s no gem command to update, and it appears
it’s not being used anyhow.
So looking at that, it doesn’t look like it’d be able to run the proper
update command…
David I get the same error. You will get a better trace by adding the
following to your pom
install cuke4duke --debug --verbose --backtrace
See also recent discussion in https://groups.google.com/forum/#!forum/cukes
I was happily cuking along, until a new developer also tried to run the
cucumber stuff, and then, since they’ve got a shiny new install without
any gems installed, it all fails miserably for them.
The first link is the only thing I’m able to find that is relevant to
this. It must be a new-ish glitch
Version information might help:
I’m using the cuke4duke maven plugin 0.4.4 and the cuke4duke gem version
0.4.3
I’ve discovered that using 0.4.2 will work, but 0.4.3 and 0.4.4 versions
of the gem will not.
David I found explicitly installing cucumber prior to cuke4duke 0.4.4
worked. The pom:
install cucumber
install cuke4duke
If it’s not a clean machine you may need to remove the maven repository
first to clean out any old gherkin gems.
rm -r ~/.m2/repository/org/jruby/; rm -r ~/.m2/repository/.jruby/
David I found explicitly installing cucumber prior to cuke4duke 0.4.4
worked. The pom:
install cucumber
install cuke4duke
If it’s not a clean machine you may need to remove the maven repository
first to clean out any old gherkin gems.
rm -r ~/.m2/repository/org/jruby/; rm -r ~/.m2/repository/.jruby/
Yep, thanks to Shawn McCarthy and Alan for this, it does indeed work.
David
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.