Converting a more complex Rails 2.3 style plugin to non-
deprecated under Rails 3.2  If you have a Rails plugin in your
./vendor/plugins/, Rails 3.2 warns you this is deprecated and
future versions of Rails will not support this. The deprecation
notice links you to an announcement that suggests you:  Extract
your vendor/plugins to their own gems and bundle them in your
Gemfile. If they’re tiny, not worthy of the own gem, fold it
into your app
as lib/myplugin/* and config/initializers/myplugin.rb.  Tiny or
not, if your plugin did not include models, views or helpers, it
was just some straight ruby logic in ‘lib’, simply moving the
files to your ./lib instead of ./vendor/plugins is pretty
straightforward, and Matt Coneybeare gives you a nice
walkthrough.   But what if your plugin does have Rails models,
helpers, views, and you don’t want to completely
rearchitect/refactor it, you just want to get it working non-
deprecated in Rails 3.2 (and future releases) as simply as
possible? And you don’t really want it to b