Hi All I've written an application using rails 1.1.8 or 1.1.6 (I'm not really sure) Anyway, I've updated rails to 1.2.1, like [code]gem update rails --include-depedencies[/code] Now when I create a new project like[code]rails newProject[/code] and I start the [b]scripts/console[/b] and type[code]Rails::VERSION::STRING[/code] I get [b]1.2.1[/b] So far so good. However, when I put all my self-written stuff inside this new project, and I repeat the exercise I get the following version number: [b]1.1.6[/b] Any suggestions how this is possible, and how to solve this ? Thnx a lot LuCa
on 2007-02-04 18:52
on 2007-02-04 19:14
I noticed that the version is hard-coded inside config/environment.rb Can I just change RAILS_GEM_VERSION = '1.1.6' to RAILS_GEM_VERSION = '1.2.1' or is that a bad idea ? LuCa
on 2007-02-04 19:18
Luca Scaljery wrote: > I've written an application using rails 1.1.8 or 1.1.6 (I'm not really > sure) > Anyway, I've updated rails to 1.2.1, like [code]gem update rails > --include-depedencies[/code] [SNIP] > So far so good. However, when I put all my self-written stuff inside > this new project, and I repeat the exercise I get the following version > number: [b]1.1.6[/b] gem update rails simply installs the most recent gems on your system. For your application to use those gems, you need to modify which version to load in config/environment.rb. -- Jakob Skjerning - http://mentalized.net
on 2007-02-04 19:20
on 2007-02-04 20:27
On that topic, is there some sort of general way to keep all the files in script/ and config/ up to date with the rails version?
on 2007-02-05 04:09
I ran into this problem a few weeks ago. If I ran ruby script\about I got 1.1.6 and running rails -v was 1.2.1. Or was it the other way around? Anyway, I was sure the update was correct. Another poster told me when the app is generated it hardcodes the original version you installed. Just change it in environment.rb and it'll match.