This project is archived and is in readonly mode.
Traditional Rails plugins should be deprecated in 3.0
Reported by Graeme Mathieson | September 1st, 2009 @ 08:49 AM
Continuing from my previous ticket #3126 the entire plugin infrastructure should be deprecated in Rails 3.0 and removed in Rails 3.1, replacing it with the gem loading mechanism for incorporating reusable extensions.
I'm sure it's not as easy as all that -- I reckon there's currently a few things that plugins do which aren't supported with the gem loading infrastructure -- but there's a huge win from getting everything to use a package management system which supports versioning and dependencies.
Deprecation messages in 3.0 will encourage plugin authors to replace their existing plugins with gems, which is definitely for the win.
Comments and changes to this ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Anders Carling
Graeme Mathieson
Jeremy Kemper