> Hi List, > We didn't resolve this in the end, we rolled back to Cucumber 0.3.0; has > anyone else seen anything similar? >
Nobody else has reported anything similar on this mailing list. Can you run with --backtrace on so we can see where the error is coming from? Can you also gist your features/support/env.rb file? Aslak > > - Lee > > 2009/4/30 Julian Leviston <[email protected]> > > I have NO idea if this is relevant, but the way you extend worlds has >> changed, I'm fairly sure. >> Julian. >> >> >> On 30/04/2009, at 10:15 PM, Lee Hambley wrote: >> >> Hi All, >> >> I'm new to the list, but a happy cucumber user with a few weeks experience >> now... a bit of a shock this morning when someone upgraded here and happened >> to jump up to 0.3.1, we're seeing the following output.. >> >> I haven't had chance to investigate more, but I will try to.. this goes >> away if we roll back to 0.3.0. >> >> - http://gist.github.com/104429 >> >> I also listed the relevant local gems as far as I can see, I'll post back >> here if I come up with anything, pointers or suggestions would be welcomed! >> >> Thank you, >> >> Lee Hambley >> >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users >> >> >> >> _______________________________________________ >> rspec-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/rspec-users >> > > > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
