This project is archived and is in readonly mode.
When a new Rails application is created by "rails new", autoload_paths instead of load_paths should be put in the generated application.rb
-
Tadatoshi Takahashi
P.S. I have just found that unless there is a Gemfile specifying rails 3.0.0.rc, rails command in any directory still uses the one for 3.0.0.beta4.
I apologize that I may have written the ticket too early and that I should investigate my environment more.
Here is what I get in the directory with the Gemfile:
$ rails --version Rails 3.0.0.rcAnd here is what I get in the directory without Gemfile:
$ rails --version Rails 3.0.0.beta4 -
Rohit Arondekar
- State changed from new to invalid
- Importance changed from to Low
-
Jeff Dean
Is there any reason not to deprecate load_paths? These seemingly arbitrary name changes, with no deprecation warnings, make it harder for people to upgrade. If I write the deprecation warning will you accept it?
-
Robert Pankowecki
I had the same issue. It took me some time to fine that the method is now called ActiveSupport::Dependencies.autoload_paths instead of ActiveSupport::Dependencies.load_paths. Please use deprecations when making such changes.