https://github.com/cucumber/gherkin/blob/master/README.md
Aslak
It seems related to this bug: https://github.com/rubygems/rubygems/pull/121
In gherkin 2.4.7 I changed the gemspes's rake_compiler version from
'>= 0.7.8' to '=0.7.9' in and hell broke loose.
I just released gherkin 2.4.9 with '0.7.9', but that doesn't seem to
have helped.
I'm going to try again with '~> 0.7.9' (trying to avoid accidental
upgrade of rake_compiler, which is a brittle part of the build
system).
Aslak
> Any more info I can provide you with?
> Cheers,
> Felix
>
> --
> You received this message because you are subscribed to the Google Groups
> "Cukes" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/cukes/-/_2JfMgQzzjsJ.
> To post to this group, send email to cu...@googlegroups.com.
> To unsubscribe from this group, send email to
> cukes+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/cukes?hl=en.
>
Allright, gherkin 2.4.11 should fix everything. RubyGems and RVM has
caused me to shave about 20 yaks.
It at least installs without complains, which is enough for me to
consider this fixed, thanks a bunch!
On Wed, Aug 17, 2011 at 11:26 AM, aslak hellesoy
<aslak.h...@gmail.com> wrote:
> On Wed, Aug 17, 2011 at 11:08 AM, Felix Schäfer
> <felix.s...@googlemail.com> wrote:
>> Hi Aslak,
>> I (@thegcat on twitter) tried again on rubygems 1.8.8, still breaks:
>> Invalid gemspec in
>> [/Library/Ruby/Gems/1.8/specifications/gherkin-2.4.8.gemspec]: Illformed
>> requirement ["#<YAML::Syck::DefaultKey:0x105815730> 0.7.9"]
>
> It seems related to this bug: https://github.com/rubygems/rubygems/pull/121
>
> In gherkin 2.4.7 I changed the gemspes's rake_compiler version from
> '>= 0.7.8' to '=0.7.9' in and hell broke loose.
> I just released gherkin 2.4.9 with '0.7.9', but that doesn't seem to
> have helped.
>
> I'm going to try again with '~> 0.7.9' (trying to avoid accidental
> upgrade of rake_compiler, which is a brittle part of the build
> system).
>Allright, gherkin 2.4.11 should fix everything. RubyGems and RVM has
caused me to shave about 20 yaks.
gem install cuke4duke --version 0.4.3
On Wednesday, August 17, 2011 5:00:52 AM UTC-6, Aslak Hellesøy wrote:On Wed, Aug 17, 2011 at 11:26 AM, aslak hellesoy
<aslak.h...@gmail.com> wrote:
> On Wed, Aug 17, 2011 at 11:08 AM, Felix Schäfer
> <felix.s...@googlemail.com> wrote:
>> Hi Aslak,
>> I (@thegcat on twitter) tried again on rubygems 1.8.8, still breaks:
>> Invalid gemspec in
>> [/Library/Ruby/Gems/1.8/specifications/gherkin-2.4.8.gemspec]: Illformed
>> requirement ["#<YAML::Syck::DefaultKey:0x105815730> 0.7.9"]
>
> It seems related to this bug: https://github.com/rubygems/rubygems/pull/121
>
> In gherkin 2.4.7 I changed the gemspes's rake_compiler version from
> '>= 0.7.8' to '=0.7.9' in and hell broke loose.
> I just released gherkin 2.4.9 with '0.7.9', but that doesn't seem to
> have helped.
>
> I'm going to try again with '~> 0.7.9' (trying to avoid accidental
> upgrade of rake_compiler, which is a brittle part of the build
> system).
>Allright, gherkin 2.4.11 should fix everything. RubyGems and RVM has
caused me to shave about 20 yaks.Yes it fixed gherkin, but I'm still seeing the same problem
attempting to install cuke4duke, either version:gem install cuke4duke --version 0.4.3
gem install cuke4duke --version 0.4.4The install cuke4duke 0.4.3 was working as recently as August 16 (our last nightly build).
--
You received this message because you are subscribed to the Google Groups "Cukes" group.
To view this discussion on the web visit https://groups.google.com/d/msg/cukes/-/oy5uZ_2AwjoJ.
On Wednesday, August 17, 2011 5:00:52 AM UTC-6, Aslak Hellesøy wrote:On Wed, Aug 17, 2011 at 11:26 AM, aslak hellesoy
<aslak...@gmail.com> wrote:
> On Wed, Aug 17, 2011 at 11:08 AM, Felix Schäfer
> <felix...@googlemail.com> wrote:
>> Hi Aslak,
>> I (@thegcat on twitter) tried again on rubygems 1.8.8, still breaks:
>> Invalid gemspec in
>> [/Library/Ruby/Gems/1.8/specifications/gherkin-2.4.8.gemspec]: Illformed
>> requirement ["#<YAML::Syck::DefaultKey:0x105815730> 0.7.9"]
>
> It seems related to this bug: https://github.com/rubygems/rubygems/pull/121
>
> In gherkin 2.4.7 I changed the gemspes's rake_compiler version from
> '>= 0.7.8' to '=0.7.9' in and hell broke loose.
> I just released gherkin 2.4.9 with '0.7.9', but that doesn't seem to
> have helped.
>
> I'm going to try again with '~> 0.7.9' (trying to avoid accidental
> upgrade of rake_compiler, which is a brittle part of the build
> system).
>Allright, gherkin 2.4.11 should fix everything. RubyGems and RVM has
caused me to shave about 20 yaks.Yes it fixed gherkin, but I'm still seeing the same problemI don't understand what you mean. Any error messages?
> I have same issue while installing 0.4.4. Are there any solutions to
> this issue?
>
What gem fails to install? cuke4duke? cucumber? gherkin?
What JRuby version do you have?
(Please don't top-post)
Aslak
> --
> You received this message because you are subscribed to the Google Groups "Cukes" group.
I am installing cuke4duke. It fails with
[ant:gem] ERROR: While executing gem ... (ArgumentError)
[ant:gem] undefined class/module YAML::Syck::DefaultKey
I have gems 1.8.10 version.
It used to work fine. It stopped yesterday.
http://blog.rubygems.org/2011/08/31/shaving-the-yaml-yacc.html
I understood this was the problem. The rubygems infrastructure is
downright pathetic. Especially when getting involved in the voodoo
magic that is cuke4duke :(
I'm encountering the same problem today trying to install nokogiri. It
worked fine in a local jruby, but doesn't work at all when the
cucumber maven plugin tries to install it.
*sigh* This is ridiculously frustrating.
David
So the problem is the same old problem that happened before. And the
fix I used to use was to downgrade cuke4duke the gem to 0.4.2.
However, that doesn't seem to be working anymore, in fact no gems are
installed using the cuke4duke-maven-plugin. It simply doesn't work
anymore.
This is really crappy. I don't think the cucumber-jvm thing is up to
par yet, as it doesn't support Background and tables. (unless that
just happened and I missed it.)
So yeah, just ranting at the stupidity that is rubygems. I now
understand why so many people got so pissed at the rubygems
developers.
David
So I have a hack and a half.
The maven stuff is installed in ~/.m2/repository/.jruby/
There's a gems dir and a specification dir.
The way I got around this was by using an rvm managed jruby.
I switched to that jruby and installed the gems I wanted by hand.
Then copy the gem folders from ~/.rvm/gems/jruby-1.6.3/gems into
~/.m2/repository/.jruby/gems
Also copy the specification files from
~/.rvm/gems/jruby-1.6.3/specifications into
~/.m2/repository/.jruby/specifications
Then you don't actually have to run -Dcucumber.installGems=true and
everything works again.
It's an uberhack of ultimate destiny, but it will get you working on
the things that are important. Delivering useful software with robust
tests :)
Hope that helps some,
David
Maybe it's just half a hack :(
I've posted that question in an effort to try and figure out what's
really going on here. I can install some gems, but not all of them. I
don't know whats causing it :(
Sorry,
David
Last time, I promise.
http://shlrm.org/wordpress/2011/09/13/using-cuke4duke-and-working-around-rubygems-issues/
I worked around the cuke4duke gem installation stuff using a maven ant
task. It's worked reliably for me today, and on a couple of other
boxes.
Perhaps it will help you out getting the gems installed.
Good luck,
David
On Sep 14, 2011 11:22 AM, "Lache...@gmail.com" <lache...@gmail.com> wrote:
> David, Have you looked at Cucumber-JVM instead? Since Cuke4Duke isn't
> being worked on anymore.
yeah, i have, it doesnt yet support background and scenario outlines, which we are using. So, i have to keep the existing cuke4duke limping along until i can change it over. Ironically, if i'd been able to spend time working on cucumber-jvm instead of fixing glitches with cuke4duke, maybe we would already be able to use it :)
Thanks,
David
Ps: not top posting is difficult with the gmail client on android, heh