Closed kredmer closed 12 years ago
Its a wild guess here, but do you have both jammit and jammit-s3 declared in Gemfile? jammit-s3 already depends on jammit, and I remember there was an issue when declaring both gems. Try with just gem 'jammit-s3'
yes, I tried with just gem 'jammit-s3' ....
OK. I found the solution.
in routes.rb I had still still line : require 'jammit'
Removing it - removed the warning.
I get a lot of warning of already initialized constants - see here: https://gist.github.com/1496980
gemfile.lock
I played with nearly all combinations in gemfile to solve this problem.
If I only use jammit there is no warning - so it must be in jammit-s3.
Any ideas?