That fixed it. Thanks so much, David!
> What I believe to be the fix is now up in github. Geetarista, would you do me
> a favor and update your gemfile to point to the git repos:
>
> gem "rspec-rails", :git => "git://github.com/rspec/rspec-rails.git&quo
Sorry about that. For some reason I thought Google Reader stripped
that automatically.
I added ":require => nil" because I had read somewhere that it was
good to do so. Can't remember why or where. Taking it out does not
fix the failure.
I just haven't upgraded Haml because it's not top priorit
Gemfile: http://gist.github.com/453032
On Jun 25, 7:41 am, Wincent Colaiuta wrote:
> El 25/06/2010, a las 15:38, geetarista escribió:
>
> > That did not fix it.
>
> What have you got in your Gemfile?
>
> Cheers,
> Wincent
>
>
That did not fix it.
On Jun 25, 3:41 am, David Chelimsky wrote:
> On Jun 24, 2010, at 11:05 PM, geetarista wrote:
>
> >http://gist.github.com/452385
>
> > (It's the default generated from rails g rspec:install).
>
> > I'm not sure what else it could be.
elimsky wrote:
> On Jun 24, 2010, at 10:36 PM, geetarista wrote:
>
>
>
>
>
> > On Jun 24, 8:21 pm, David Chelimsky wrote:
> >> On Thu, Jun 24, 2010 at 10:12 PM, geetarista wrote:
>
> >>> On Jun 24, 7:10 pm, David Chelimsky wrote:
> >>&g
Here's the backtrace and the spec file: http://gist.github.com/452355
Also, if I delete that spec file, it just goes to the next
alphabetical file and gives the same error for that model name.
On Jun 24, 8:21 pm, David Chelimsky wrote:
> On Thu, Jun 24, 2010 at 10:12 PM, geetarist
I'm using Rails master.
On Jun 24, 7:10 pm, David Chelimsky wrote:
> On Jun 24, 2010, at 2:24 PM, geetarista wrote:
>
> > On Jun 24, 12:03 pm, David Chelimsky wrote:
> >> On Jun 24, 2010, at 1:23 PM, geetarista wrote:
>
> >>> I just upgraded to beta.13 a
I did both 'bundle install' and 'bundle update'.
On Jun 24, 12:03 pm, David Chelimsky wrote:
> On Jun 24, 2010, at 1:23 PM, geetarista wrote:
>
> > I just upgraded to beta.13 and I'm running into an issue where when I
> > run 'rake spec&#
I just upgraded to beta.13 and I'm running into an issue where when I
run 'rake spec', I get an 'uninitialized constant Comment' error.
Comment is the first model (alphabetically) in my project. If I
switch back to beta.12, it works. If I use 'spec .' and not 'rake
spec', it also works.
Environm
Awesome. Thanks for the clarification!
On Jun 10, 1:10 pm, David Chelimsky wrote:
> On Thu, Jun 10, 2010 at 3:14 PM, geetarista wrote:
> > Since Rspec-Rails 2 is specifically geared toward Rails 3, I'm
> > wondering why it doesn't use railtie, the new generators, etc.
Since Rspec-Rails 2 is specifically geared toward Rails 3, I'm
wondering why it doesn't use railtie, the new generators, etc. Will
it stay this way or is it planned to support that?
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.
I'm having similar issues, but when I run the CMD + R command in
Textmate:
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such
file to load -- spec (LoadError) from /System/Library/Frameworks/
Ruby.framework/Vers
12 matches
Mail list logo
