It is now a requirement for attachments to do one of three things:
  1. Have a content_type validation (e.g. "image/*")
  2. Have a filename validation (e.g. *.png, *.gif)
  3. Explicitly *not* have one of those validations

The intent is to make the default more secure, and you have to
explicitly reject the security of a validation in order to not have one.

There was a spec that was failing because we removed .attachment_definitions
from models, I expected this to fix it, but apparently it hasn't.

This is for Rails 3.1+

Needs work for S3 Attachments.

This is necessary so Gemnesium will be green.

The original commit came from @amazonwebservices and @trevorrowe in #579.
I had to revise the commit and make sure all the test cases are passing.
All credits still goes to those guys, thanks a lot!

This will fix the problem on the CI server, where some time the change occurred by "write_file" will not trigger Rubinius to generate a compiled .rbc file.

This test will generate a basic Rails application, include Paperclip
into Gemfile, and call basic `has_attached_file` in the model. This will
make sure that we're not messing up any of the configuration and
integration for our gem and the Rails framework.