Rails::VERSION::STRING shows 1.1.6, but 1.2.1 expected

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 gem update rails --include-depedencies

Now when I create a new project likerails newProject
and I start the scripts/console and
typeRails::VERSION::STRING
I get 1.2.1
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: 1.1.6

Any suggestions how this is possible, and how to solve this ?

Thnx a lot
LuCa

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

Luca S. 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 gem update rails --include-depedencies
[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: 1.1.6

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 S. - http://mentalized.net

http://blog.kogent.net/2007/01/18/rails-12-released-gems-pushed-life-is-good/

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?

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.