I tried to remove Rails 2.0PR1 entirely from /vendor/rails (rake rails:unfreeze) which gives exactly the same stack trace with the same line numbers. This confirms your theory that the numbers correspond to 1.2.5 (installed as gem on my machine).
> rake rails:unfreeze > ruby script\server => Booting Mongrel (use 'script/server webrick' to force WEBrick) => Rails application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... Exiting c:/ruby/lib/ruby/gems/1.8/gems/rails-1.2.4/lib/initializer.rb:334:in `send': undefined method `session=' for ActionController::Base:Class (NoMethodError) from c:/ruby/lib/ruby/gems/1.8/gems/rails-1.2.4/lib/initializer.rb: 334:in `initialize_framework_settings' from c:/ruby/lib/ruby/gems/1.8/gems/rails-1.2.4/lib/initializer.rb: 333:in `each' .... Koz wrote: > The line numbers in your stack traces correspond directly to the 1.2.5 > / 1-2-stable initializer. So either you've made a mistake and checked > the wrong thing out to vendor/rails, or it's picking up the gems > irrespective of vendor/rails being there. > > Can you try: > > 1) removing the RAILS_GEM_VERSION constant entirely. > 2) manually checking out the latest edge and the release tags. > If i uncomment the RAILS_GEM_VERSION and update from trunk, it works. So everything is fine. Thanks for your time and effort. I'm glad this isn't a bug in Rails 2. /Jesper www.justaddwater.dk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
