This project is archived and is in readonly mode.
rake doc:rails doesn't know how to build taks actionmailer...README
-
Sam Ruby
Symptoms have changed since this ticket was opened. New symptoms:
$ rake doc:rails (in /home/rubys/svn/rails4/Book/util/work/dummy_app) rake aborted!
spec rack-mount-0.6.0 is not from an installed gem
/home/rubys/svn/rails4/Book/util/work/dummy_app/Rakefile:4 (See full trace by running task with --trace) -
Jeremy Kemper
- State changed from new to open
Need to walk the gemspecs and use their rdoc paths rather than checking for frozen gems.
-
Jorge Dias
I ran the rake task without any problem, using rails3 beta3
-
Tim Rosenblatt
No problems running
rake doc:railsunder beta3 -
Daniel Mavis
- Importance changed from to Low
No problems running
rake doc:railson beta4 (ruby 1.9.2-rc1). Some warnings though:(in /Users/mavi/dev/projects/maps) rm -r doc/api invalid options: --line-numbers, --inline-source (invalid options are ignored) Parsing sources... /Users/mavi/.rvm/gems/ruby-1.9.2-rc1/gems/actionpack-3.0.0.beta4/lib/action_view/helpers/tag_helper.rb:18:66: 'attr' ignored - looks like a variable /Users/mavi/.rvm/gems/ruby-1.9.2-rc1/gems/actionpack-3.0.0.beta4/lib/action_view/helpers/tag_helper.rb:18:73: 'attr' ignored - looks like a variable /Users/mavi/.rvm/gems/ruby-1.9.2-rc1/gems/activesupport-3.0.0.beta4/lib/active_support/deprecation/proxy_wrappers.rb:61:15: Expected class name or '<<'. Got RDoc::RubyToken::TkIDENTIFIER: "target" 100% [427/427] ...vm/gems/ruby-1.9.2-rc1/gems/railties-3.0.0.beta4/lib/rails.rbEdited by Rohit Arondekar for formating.
-
Trotter Cashion
No problems running rake doc:rails under rc1. Ruby 1.8.7
-
Ryan Bigg
Automatic cleanup of spam.
-
Cesario
rake rdocis working just fine with current master. We can safely close that ticket IMHO. -
Rohit Arondekar
Cesario, but does it work on 3.0.3 or the 3-0-stable branch?
-
Piotr Sarnacki
I checked on both 3.0.3 and 3-0-stable and it works fine for me.
-
Rohit Arondekar
- State changed from open to resolved
Feel free to leave a comment if anybody else finds the same issue again, and I'll reopen the ticket.