collectiveidea / delayed_job_active_record

ActiveRecord backend integration for DelayedJob 3.0+
MIT License
346 stars 336 forks source link

rails g delayed_job:upgrade fails under Rails3.2 #11

Closed nbt closed 12 years ago

nbt commented 12 years ago

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 message Could not find generator delayed_job:upgrade. I am:

$ bundle install
Using rake (0.9.2.2) 
Using ZenTest (4.6.2) 
Using i18n (0.6.0) 
Using multi_json (1.0.4) 
Using activesupport (3.2.0) 
Using builder (3.0.0) 
Using activemodel (3.2.0) 
Using erubis (2.7.0) 
Using journey (1.0.1) 
Using rack (1.4.1) 
Using rack-cache (1.1) 
Using rack-test (0.6.1) 
Using hike (1.2.1) 
Using tilt (1.3.3) 
Using sprockets (2.1.2) 
Using actionpack (3.2.0) 
Using mime-types (1.17.2) 
Using polyglot (0.3.3) 
Using treetop (1.4.10) 
Using mail (2.4.1) 
Using actionmailer (3.2.0) 
Using arel (3.0.0) 
Using tzinfo (0.3.31) 
Using activerecord (3.2.0) 
Using activeresource (3.2.0) 
Using addressable (2.2.6) 
Using annotate (2.4.0) 
Using encryptor (1.1.3) 
Using attr_encrypted (1.2.0) 
Using autotest (4.4.6) 
Using bcrypt-ruby (3.0.1) 
Using bluecloth (2.2.0) 
Using bundler (1.0.21) 
Using cancan (1.6.7) 
Using crack (0.3.1) 
Using daemons (1.1.6) 
Using delayed_job (3.0.1) 
Using delayed_job_active_record (0.2.1) 
Using orm_adapter (0.0.6) 
Using rack-ssl (1.3.2) 
Using json (1.6.5) 
Using rdoc (3.12) 
Using thor (0.14.6) 
Using railties (3.2.0) 
Using warden (1.1.0) 
Using devise (2.0.0) 
Using diff-lcs (1.1.3) 
Using unf_ext (0.0.4) 
Using unf (0.0.4) 
Using domain_name (0.5.2) 
Using eventmachine (0.12.10) 
Using jquery-rails (2.0.0) 
Using net-http-digest_auth (1.2) 
Using net-http-persistent (2.3.3) 
Using nokogiri (1.5.0) 
Using ntlm-http (0.1.1) 
Using webrobots (0.0.13) 
Using mechanize (2.1) 
Using pg (0.12.2) 
Using rails (3.2.0) 
Using rspec-core (2.8.0) 
Using rspec-expectations (2.8.0) 
Using rspec-mocks (2.8.0) 
Using rspec (2.8.0) 
Using rspec-rails (2.8.1) 
Using ruby-graphviz (1.0.3) 
Using ruby-prof (0.10.8) 
Using thin (1.3.1) 
Using vcr (1.11.3) 
Using webmock (1.7.10) 
Using webrat (0.7.3) 
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.

$ rails g delayed_job:upgrade
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)
Could not find generator delayed_job:upgrade.

(FWIW, I believe the deprecation warning is a rake problem, not a delayed_job problem.)

nbt commented 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.

betamatt commented 12 years ago

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.

nbt commented 12 years ago

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!