# Upgarde from rails 2.3.5 to rails 2.3.8

**URL:** <https://www.ruby-forum.com/t/upgarde-from-rails-2-3-5-to-rails-2-3-8/193474>\
**Category:** Rails\
**Created:** [August 18, 2010, 12:11pm UTC](https://www.ruby-forum.com/t/upgarde-from-rails-2-3-5-to-rails-2-3-8/193474 "2010-08-18T12:11:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tom-mac](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/bc8723/32.png) [@tom-mac](https://www.ruby-forum.com/u/tom-mac)\
**Post date:** [August 18, 2010, 12:11pm UTC](https://www.ruby-forum.com/t/upgarde-from-rails-2-3-5-to-rails-2-3-8/193474/1 "2010-08-18T12:11:05Z")

</div>

Hi

I upgraded my rails application rails 2.3.8 from 2.3.5 like below

gem install rails -v=2.3.8

```
Now in environemnt.rb RAILS_GEM_VERSION changed to '2.3.8'. Now

```

when I tried to a previous migration like

rake db:migrate VERSION=20100714122104

```
 I got warning like

```

DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed\_job/tasks,  
vendor/plugins/paperclip/tasks, vendor/plugins/seed-fu/tasks,  
vendor/plugins/simple\_captcha/tasks, vendor/plugins/tabs\_on\_rails/tasks,  
and vendor/plugins/xss\_terminate/tasks are deprecated. Use lib/tasks  
instead. (called from  
/usr/lib/ruby/gems/1.8/gems/rails-2.3.8/lib/tasks/rails.rb:10)

```
 I would like to know why this message shown? Is it any problem? If

```

it is, how to resolve it?

Thanks

---

<div class="post-metadata">

**Author:** ![tom-mac](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/bc8723/32.png) [@tom-mac](https://www.ruby-forum.com/u/tom-mac)\
**Post date:** [August 18, 2010, 3:35pm UTC](https://www.ruby-forum.com/t/upgarde-from-rails-2-3-5-to-rails-2-3-8/193474/2 "2010-08-18T15:35:02Z")

</div>

2.3.8 attempts to give deprecation notices for things which will go away  
in Rails 3.0 & later. In this case it is saying that several of your  
plugins should place their rake tasks into the lib directory. While  
this won’t cause any problems in your app, it is good to start resolving  
the warnings to be better prepared for future updates. You may also  
want to consider using the gem versions of those plugins if available as  
that will also eliminate the deprecation notices. Also with Bundler,  
the days of needing to vendor gems are for the most part gone. You can  
use Bundler with 2.3.8 (I am) & it can make things much easier for you  
in terms of dependency management.

Niels