jammit-s3 does not play nice with paperclip when storage is set to s3

[jspillers]

Paperclip uses the aws-s3 gem to handle image uploads to your bucket. Jammit-s3 apparently uses a different gem that does not get along with aws-s3... i think they share some similar namespaces and are colliding.

specifically i am getting this error when i try to upload a file:

NoMethodError (undefined method `exists?' for AWS::S3::S3Object:Class)

Would be awesome if these two gems could co-exist as I definitely have need for both.

[kmamykin]

I dont know how others have solved this issue, may be there is a better solution, but I had to migrate jammit-s3 gem to use aws-s3 gem. There is already a fork by someone.

[simonoff]

Why? s3 gem works fine. Use https://github.com/qoobaa/s3/blob/master/extra/s3_paperclip.rb file for support S3 storage.
Just now I'm working on invalidation support for s3_paperclip.rb.

[kmamykin]

Ah, admittedly I did not put much time into researching the issue. s3_paperclip might have solved it.

[jaredmoody]

So the solution for this is to monkey patch paperclip? I'd rather not . . .

[simonoff]

For me it's the best way. Why I need depend my app on two modules with the same functionality?