Hallo -- I can''t run any rake tasks all of a sudden in my project. It was fine when I put it down the other day! The output I get when I try to run a rake task is: <output> W:\holly> rake in W:/holly) rake aborted! uninitialized constant ActiveRecord W:/holly/rakefile:10 (See full trace by running task with --trace) </output> Can anyone shed any light on this? I''m hamstrung w/out rake! Cheers, Doug. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Hi -- sorry, should have said -- it''s a standard RoR rakefile. The contents are: <code> # Add your own tasks in files placed in lib/tasks ending in .rake, # for example lib/tasks/capistrano.rake, and they will automatically be available to Rake. require(File.join(File.dirname(__FILE__), ''config'', ''boot'')) require ''rake'' require ''rake/testtask'' require ''rake/rdoctask'' require ''tasks/rails'' </code> Line 10 is the last line, & it calls all Rails framework stuff, so I don''t think it''s anything I''ve done. Cheers, Doug. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Got it! It was one of my custom rake tasks! The damn'' thing had never worked properly, & I''d clean forgotten about it -- it was requiring a non-existant file & silently exiting, so I just zapped it, & all''s well w/ the world. The amount of time I could''ve saved by remembering to run "rake --trace" in the first place... Cheers for your input. Doug. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---