Databases
StackOverflow2013
Postsdbo
PORails: how do I resolve the 'rake/rdoctask'' is deprecated' warning?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails: how do I resolve the 'rake/rdoctask'' is deprecated' warning?
    primarykey
    data
    text
    <p>Just a forewarning: I'm a rails noob.</p> <p>When I run:</p> <pre><code>rake db:migrate </code></pre> <p>I get this deprecation warning:</p> <pre><code>WARNING: 'require 'rake/rdoctask'' is deprecated. Please use 'require 'rdoc/task' (in RDoc 2.4.2+)' instead. at /Users/username/Code/rails/appname/rake/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/rdoctask.rb </code></pre> <p>I'm using:</p> <ul> <li>Rails 3.0.1 </li> <li>Rake 0.9.2.2 </li> <li>RSpec 2.0.1 </li> <li>RDoc 3.12</li> </ul> <p>If I uninstall rake 0.9.2.2 and use 0.8.7 there's no warning, but I rather not count that as a solution. </p> <p>After a google search, many sites say I need to update a line in my Rakefile (basically changing require ‘rake/rdoctask’ to require ‘rdoc/task’). However, my Rakefile looks like this:</p> <pre><code>require File.expand_path('../config/application', __FILE__) require 'rake' AppName::Application.load_tasks </code></pre> <p>There's no require statement to replace. When I add require 'rdoc/task', it has no effect. When I search the project for the deprecated 'rake/rdoctask', there are no results. So why is rails complaining?</p> <p><strong>edit:</strong> Not sure if it matters, but here's my gemfile:</p> <pre><code>source 'http://rubygems.org' gem 'rails', '3.0.1' gem 'sqlite3-ruby', :require =&gt; 'sqlite3' group :development, :test do gem 'rspec-rails', '2.0.1' gem 'annotate-models', '1.0.4' end group :test do gem 'rspec', '2.0.1' gem 'webrat', '0.7.1' gem 'spork', '0.8.4' end </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser2393462435
    1. USuser2393462435
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails: how do I resolve the 'rake/rdoctask'' is deprecated' warning?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails: how do I resolve the 'rake/rdoctask'' is deprecated' warning?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORails: how do I resolve the 'rake/rdoctask'' is deprecated' warning?
      1. USDominick
      1. VTFavorite
    1. COtry `bundle exec rake db:migrate`
      singulars
      1. PORails: how do I resolve the 'rake/rdoctask'' is deprecated' warning?
      1. USclyfe
    2. CObundle exec rake db:migrate gives me the same warning.
      singulars
      1. PORails: how do I resolve the 'rake/rdoctask'' is deprecated' warning?
      1. USuser2393462435
    3. COThis warning often follows a GEM that is failing to load or not properly packaged. Do you have any require statements in your migrations or could you post your Gemfile? Update: sorry, long night... just saw the require statements in your OP
      singulars
      1. PORails: how do I resolve the 'rake/rdoctask'' is deprecated' warning?
      1. USScottJShea
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload