C. Zona wrote in post #1027966:
> Those paths suggest that you may be using Ruby 1.9.1, which has lots
> of gnarly bugs (and won't work at all with Rails 3.0, if that's
> relevant for you).  If you have the option, switch to 1.9.2 or 1.8.7.
>
> For this particular 1.9.1 issue, I've had success on 'nix and OSX by
> calling "Gem.loaded_specs" before requiring the gem.  See if that
> works for you too.

I am using 1.9.2
Pretty sure of it. =)

-- 
Posted via http://www.ruby-forum.com/.