upgrading to rails 3.

I've installed rails_upgrade plugin with ruby script/plugin install http://github.com/rails/rails_upgrade.git. Then if I run rake rails:upgrade:check it says rake aborted! no such file to load -- initializer

What I've missed?

Msan Msan wrote:

I've installed rails_upgrade plugin with ruby script/plugin install GitHub - rails/rails_upgrade: Plugin to run checks on your Rails 2.x/3.x to check for obvious upgrade points on the path to 3.0. Then if I run rake rails:upgrade:check it says rake aborted! no such file to load -- initializer

What I've missed?

I just went through running rails_upgrade last night. I don't remember running into this problem. But, I wanted to ask if you were following along with Ryan Bates' Railscast on using the gem.

I just followed along and my upgrade went pretty well actually. The only major difference from what he shows and what I did was that now there is a pre-release of will_paginate that works with Rails 3.0. I simply specified the newer gem version in my gemfile instead of using the hack Ryan shows to get around the problem.

Now I still have a lot of work to do to get my application fully up on Rails 3.0. Unfortunately, I was still using a lot of old plugins that I'll finally be replacing with newer, better, solutions. But, as for the assistance rails_upgrade provides things went pretty smoothly.

try adding trace to your rake command to get more information

rake rails:upgrade:check --trace

Here is with --trace option:

rake aborted! no such file to load -- initializer /home/user/jruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /home/user/jruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /home/user/NetBeansProjects/myapp/config/boot.rb:55:in `load_initializer' /home/user/NetBeansProjects/myapp/config/boot.rb:38:in `run' /home/user/NetBeansProjects/myapp/config/boot.rb:11:in `boot!' /home/user/NetBeansProjects/myapp/config/boot.rb:110 /home/user/NetBeansProjects/myapp/config/boot.rb:31:in `require' /home/user/jruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /home/user/NetBeansProjects/myapp/Rakefile:4 /home/user/NetBeansProjects/myapp/Rakefile:2383:in `load' /home/user/jruby-1.5.2/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2383:in `raw_load_rakefile' /home/user/jruby-1.5.2/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2017:in `load_rakefile' /home/user/jruby-1.5.2/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /home/user/jruby-1.5.2/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2016:in `load_rakefile' /home/user/jruby-1.5.2/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2000:in `run' /home/user/jruby-1.5.2/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /home/user/jruby-1.5.2/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /home/user/jruby-1.5.2/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /home/user/jruby-1.5.2/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:19:in `load' /home/user/jruby/bin/rake:19

I don't know what is the problem.

Msan Msan wrote in post #937930:

I've installed rails_upgrade plugin with ruby script/plugin install GitHub - rails/rails_upgrade: Plugin to run checks on your Rails 2.x/3.x to check for obvious upgrade points on the path to 3.0. Then if I run rake rails:upgrade:check it says rake aborted! no such file to load -- initializer

What I've missed?

I'm having the exact same problem. I would have loved to see the answer here.

Ruby Man wrote in post #989320:

Msan Msan wrote in post #937930:

I've installed rails_upgrade plugin with ruby script/plugin install GitHub - rails/rails_upgrade: Plugin to run checks on your Rails 2.x/3.x to check for obvious upgrade points on the path to 3.0. Then if I run rake rails:upgrade:check it says rake aborted! no such file to load -- initializer

What I've missed?

I'm having the exact same problem. I would have loved to see the answer here.

Hello!

Can anyone tell me if this problem was resolved?

thank you

Try re-installing rails version that you are using, if you have frozen rails in your vendor directory, then remove it and use rails from gem or remove it and re-freeze

Most probably this issue is because rails is not installed properly or is not in the right path or has gotten corrupted somehow.