On 11/12/07, Chad Woolley <[EMAIL PROTECTED]> wrote: > > On 11/12/07, Rob Sanheim <[EMAIL PROTECTED]> wrote: > > Are you sure you are really upgrading to 1.2.5, and not 1.2.5.blah? > > If you are using RAILS_GEM_VERSION to set your rails version (not > > vendor/rails), you may actually be using the 2.0 prerelease if you > > aren't careful. > > > > There was a fix that went into 1.2.5 to boot.rb to fix this issue... > > Yes. First, see if you have a gem rails-1.2.5.xxxx installed on your > machine. If you do, then you probably have a problem. To confirm, do > a 'p $:' at the end of environment.rb. If you see that gem on your > load path, then that's definitely the problem. > > Uninstall the offending beta gem, then upgrade to the real 1.2.5 (not > 1.2.5.xxxx), and also update your boot.rb using 'rake > rails:update:configs' to avoid the problem in the future. > > FYI, this ticket [ http://dev.rubyonrails.org/ticket/10074 ] seeks to > avoid this issue in the future, and seems to have helped, since the > new beta gem is 1.99.0. I think 2.0.0.<revision> would have been a > better choice myself, but oh well :)
Well then it would've loaded in front of 2.0.0, right? I think that's why 1.99 was chosen. -- Rick Olson http://lighthouseapp.com http://weblog.techno-weenie.net http://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
