Hello, Why do we have to put "rails/init.rb" into a gem and not simply "init.rb" in main dir of a gem to make it behave like a plugin? Are there some special reasons for that?
It would be cool to have one codebase which can be packaged as a gem or used as a classic plugin. On the other hand, some say (and I agree) plugins will perish in favor of gems - maybe we just should wait, or speed this process up by converting plugins into gems and not allowing to use them in old way by leaving only "rails/init.rb" and deleting "init.rb" from main dir? Cheers, Jacek --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
