Closed nbt closed 12 years ago
More info:
When I include:
gem 'delayed_job_active_record'
in my Gemfile, I get the following:
$ bundle install
... lots of messages
$ rake <any command>
DEPRECATION WARNING: Calling set_table_name is deprecated. Please use `self.table_name = 'the_name'` instead. (called from <top (required)> at /Users/me/myapp/config/application.rb:7)
When I remove the delayed_job_active_record
gem from my Gemfile, the deprecation warning stops.
So it appears that the delayed_job_active_record gem is the source of the deprecation message. I don't know if that's related to the Could not find generator
problem.
I believe the deprecation will be fixed in next release. It's harmless anyway.
As far as the generator, it's not present until 0.3.0. I see you are using 0.2.1.
Yah, I just did a 'bundle update' and noticed that I'd be running the older version. (But in the meantime I looked at the sources and created my own migration to add the :queue field...not difficult.) Thanks!
Summary:
Upgrading from DJ 2.1.4 / Rails 3.0 to DJ 3.0 / Rails 3.2 fails in
rails g delayed_job:upgrade
with the messageCould not find generator delayed_job:upgrade.
I am:To replicate:
(FWIW, I believe the deprecation warning is a rake problem, not a delayed_job problem.)