Hi there, Running doc:rails and doc:rerails on a fresh rails directory after running ''rake freeze_gems'' fail with the following error: > Don''t know how to build task ''vendor/rails/activesupport/README'' Should it work? That file doesn''t seem to exist. If that''s not the sequence for generating the api documentation, what should it be? -- Alex
I''m a noob, so don''t take my answer as final, but I use ''rake appdoc'' successfully. -- Posted via http://www.ruby-forum.com/.
Damien Timewell wrote:> I''m a noob, so don''t take my answer as final, but I use ''rake appdoc'' > successfully. >That generates the documentation for a given application. I want the API docs, as presented at http://api.rubyonrails.org. rake -T lists rake doc:rails and rake doc:rerails as options, but neither of them works - at least, not the way I''m expecting, which may well be wrong. This is rails 1.1.2 on Ruby 1.8.4. -- Alex
Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2156 bytes Desc: not available Url : http://wrath.rubyonrails.org/pipermail/rails/attachments/20060506/a2fd1c91/smime.bin
Dave Thomas wrote:> On May 6, 2006, at 2:27, Alex Young wrote: >> Running doc:rails and doc:rerails on a fresh rails directory after >> running ''rake freeze_gems'' fail with the following error: >> >> > Don''t know how to build task ''vendor/rails/activesupport/README'' >> >> Should it work? That file doesn''t seem to exist. >> > Just say "echo hello >vendor/rails/activesupport/README'' and then rerun > > I mentioned this to the team when I was writing about generating > documentation for the book, and the next release will include the README > in the Gem. In the meantime, creating a dummy file allows the > documentation to proceed.Excellent. Thanks for that. -- Alex