I agree we should de-emphasize plugins, but continue to support them. Besides changing the guides, the generator should create plugins that are on the road to becoming gems. The concept being that you are creating an "unpolished gem" more than a "plugin". If we make it easy to take that final step to get to a gem, plugins will fade away.
Here are my suggestions: 1. put default Gem::Specification and Rake::GemPackageTask in the Rakefile 2. generate rails/init.rb, Gemfile, and maybe even .gemspec 3. stop generating install.rb and uninstall.rb 4. change "rails generate plugin ..." to "rails generate gem ..." (and add a deprecation notice on "rails generate plugin") In a related tangent, I also wonder whether the lower-profile of plugins has caused vendor/* to lose its usefulness. Could everything in vendor/ move to lib/? It might just require some tweaks the autoloaded paths. lib/ could become the single directory for storing all non-application, non-Bundler, libraries of code. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
