jasmine init returns 'could not find rails <>= 3.0> amongst...'

[nieve]

jasmine init returns 'could not find rails <>= 3.0> amongst...'

[peterzhao]

I got the same issue.

[nieve]

ok, at home I've got version 1.0.2.1 which works, but I also have rails 2.3.8, so I'm not sure whether this is a bug or not...

[peterzhao]

I traced the issue and found the following code in lib/jasmine/base.rb which cause the issue:

begin
Gem::Specification::find_by_name "rails", ">= 3.0"
rescue
Gem.available? "rails", ">= 3.0"
end

Line 51 ' Gem::Specification::find_by_name "rails", ">= 3.0"' will throw exception. However ruby 1.9.2p290 begin/rescue does not work and the exception will bubble up and cause 'require "jasmine"' failure. Very strange behaviour of ruby! This issue cannot be noticed on ruby 1.9.2p180.

[peterzhao]

found the solution to fix the issue:

def self.rails3?
return Rails.version.split(".").first.to_i == 3 if defined? Rails
begin
Gem::Specification::find_by_name "rails", ">= 3.0"
rescue Gem::LoadError
false
rescue
Gem.available? "rails", ">= 3.0"
end
end

need rescue Gem::LoadError exception! Will post the patch.

[nieve]

Peter- brilliant stuff!! thanks a lot, appreciate that :)

[ragaskar]

Hey, thanks for this; we've had this problem reported but haven't been able to repro it. I'm on vacation at the moment (coming to you courtesy of satellite from the New Mexico mountains), but I will merge a fix for this ASAP as soon as I'm back (later this week). I just need to test that any fix stays compatible with previous Rubygem versions.

[laripk]

Just wanted to note that I have this problem too (sinatra application, ruby 1.9.2p180 [contrasting with peterzhao's statement], jasmine 1.1.0), and came up with a similar fix. Looking forward to the patch merge.

[ragaskar]

I believe this should be fixed with the merging of #56 into the jasmine 1.1.1 gem. Let me know if you're still seeing issues.

[mraaroncruz]

Could you push this to rubygems. I just spent a bunch of time trying to debug this, then luckily found this thread.
This fix is working for me.
Thanks!