Hello, since i am using delayed_jobs as a seperate gem and thinking sphinx also bundles this library in it's vendor lib, i get the following warnings on e.g. console startup
/opt/ruby-enterprise-1.8.6-20080810/lib/ruby/gems/1.8/gems/tobi- delayed_job-1.7.0/lib/delayed/job.rb:8: warning: already initialized constant MAX_ATTEMPTS /opt/ruby-enterprise-1.8.6-20080810/lib/ruby/gems/1.8/gems/tobi- delayed_job-1.7.0/lib/delayed/job.rb:9: warning: already initialized constant MAX_RUN_TIME /opt/ruby-enterprise-1.8.6-20080810/lib/ruby/gems/1.8/gems/tobi- delayed_job-1.7.0/lib/delayed/job.rb:24: warning: already initialized constant NextTaskSQL /opt/ruby-enterprise-1.8.6-20080810/lib/ruby/gems/1.8/gems/tobi- delayed_job-1.7.0/lib/delayed/job.rb:25: warning: already initialized constant NextTaskOrder /opt/ruby-enterprise-1.8.6-20080810/lib/ruby/gems/1.8/gems/tobi- delayed_job-1.7.0/lib/delayed/job.rb:27: warning: already initialized constant ParseObjectFromYaml The question is why delayed_job must be bundled within thinking sphinx at all instead of accessing the individual gem which the user must then install to use ts? Also is there a painless possibility to avoid the warnings without touching either of the two gems, e.g. by configuration or some rails code in environment.rb or in an initializer? Greets -act --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en -~----------~----~----~----~------~----~------~--~---
