You shouldn't be seeing this problem with 2.3.2 - I just tried it in a fresh Rails app using the 2.3.2 gem. Something weird's going on in your version, as the install task sets $gems_rake_task which *should* prevent the display of the error message you're seeing.
Do you happen to have an RC version frozen in vendor/rails? That's my next guess... --Matt Jones On Jun 27, 2:51 pm, Troels Knak-nielsen <rails-mailing-l...@andreas- s.net> wrote: > Matt Jones wrote: > > What version of rails are you running? > > 2.3.2 > > I found out what the problem is though. Some gems are loaded by the > Rails initializer, so if they are missing, the rake tasks can't be > loaded. It's a catch-22 really. I wrote a wrapper script to fix it. If > any body else needs it, you can get it from here: > > http://gist.github.com/136461 > > Just put in `script/install_gems` and remember to `chmod +x`. > > -- > troels > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
