On Nov 22, 10:10 am, Schalk Neethling <[EMAIL PROTECTED]>
wrote:
> Hi All,
>
> I found the following discussion on the group:
>
> I now see this is a deprecated and now removed attribute. However, what
> I was wondering, isn't running rake rails:update supposed to fix these
> issues. From Aptana it states that rails:update does the following:
>
> Update both configs, scripts and public/javascripts from Rails
>
> Seeing that the files that contained the removed attribute is in the
> config/environments folder I find it strange that the Rake command did
> not fix it or, am I misunderstanding what exactly the command does?
editing a user editable and often heavily modified file like
production.rb would be somewhat error prone. As far as I can remember
the only such file that is updated is boot.rb (which has a warning at
the top saying 'don't change me')
Fred
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@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-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
