from
/opt/local/lib/ruby/gems/1.8/gems/cucumber-0.1.13/bin/../lib/cucumber/rails/world.rb:18
Here's line 18:
Dispatcher.class_eval do
def self.failsafe_response(output, status, exception = nil)
raise exception
end
end
I would do the following:
1) Try it with gem rails on the old project
2) If that works, then maybe removing then re-adding vendor/rails will do
the trick.
3) If that doesnt work, then maybe try messing with that file above and see
what's going wrong.
M
On Tue, Dec 23, 2008 at 2:13 PM, Maurício Linhares <
[email protected]> wrote:
> On Tue, Dec 23, 2008 at 7:04 PM, s.ross <[email protected]> wrote:
> > Hello--
> >
> > A bit stranger than that, I'm afraid. A fresh Rails project works with
> > cucumber right out of the box. This older one, recently upgraded to
> 2.2.2,
> > has the problem with dependencies.rb. The main difference is that the
> fresh
> > project is using gem rails and the real one vendor rails.
> >
> > I was hoping this would be one of those d'oh! kind of problems that
> everyone
> > knew the answer to :)
> >
>
> Geez.
>
> Same trouble here. In a blank project everything works out of the box,
> on the real project (with a vendored rails 2.2.2) it just doesn't
> work. And only in testing, the application itself runs completely
> fine.
>
> -
> Maurício Linhares
> http://alinhavado.wordpress.com/ (pt-br) | http://blog.codevader.com/ (en)
> _______________________________________________
> 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
