dmitry/has_translations — pull request #14 by Titinux (2012-02-29 14:31:55+00:00)
Title: Pretty big refactoring to prevent collisions with other gems in Rails 3.2

Hi,

I was facing a problem with the 0.3.5 version of HasTransalations. In Rails 3.2 this gem prevent other gems to apply their additions to ActiveRecord::Base. (ex : Carrierwave)

Main changes :

* Drop old plugin style code (plugin support is deprecated and will be remove soon)
* Drop Rails 3.2.x compatibility (This is first due to to ActiveSupport::Concern use but Rails 3.0 is quite old now and the 0.3.5 is still available for 2.3.x Rails versions)
* Use railtie to cleanly apply additions to ActiveRecord::Base
* Rename translations methods to has_translation to prevent shadowing with translations relation.

Test are all green with rails 3.0.11 and 3.2.1. The README has been updated to reflect changes.

I have pushed the version to 1.0.0.alpha.1 because with a little more work this gem will be stable and contains all wanted functionalities for a 1.0 version. (TODO : Add initializer file support to allow user to define app wide configuration, add generators for initializer file and migrations, ...)

I know this is a pretty big set of changes but I think this is necessary to make has_translations play well with other gems.