I'm writing a rails plugin, and figured I'd do it as a GemPlugin to be ahead of the curve. I need to install some assets when the plugin is installed in a rails app, but it would seem there's no mechanism by which this occurs; install.rb is never run for a GemPlugin, unless I'm missing something entirely.
I could check for the assets in init.rb and copy them over if they don't exist, but that strikes me as poor behavior. I would guess the thing to do would be to create a new gems task, gems:plugin:install or similar, which would invoke the install scripts on all config.gems that have been tagged with :plugin => true. Before I dive in and give this a whirl, though, I figured I'd check with the dev team and see if a. I've overlooked an existing installation mechanism, b. someone already had something in the works, or even c. the GemPlugin idea was still considered to be the future of plugins, or if yet another strategy was being considered. - donald --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
