What if you simply add the additional plugins to your main application? At least this is what I'm doing... I have 30+ engine plugins which partly depend on each other. So we add whatever is required to the main application. For testing each engine plugin still has to reference all needed plugins but this is a different topic.
Daniel On Mar 7, 7:33 pm, Tristan <tristanmchar...@gmail.com> wrote: > Hi all > > I have a plugin which itself needs to load some plugins from its own > vendor/plugins directory. > > I've spent half of this morning Googling about for answers but I > haven't found anything suitable yet. > > I've been looking at adding plugin load paths to the host app's > initializer object from init.rb but, of course, that'll be useless > seeing as being in init.rb means that the plugin loader is already > running. > > Does anyone know of a solution that can be incorporated into a > plugin's init.rb file that'll load these "nested" plugins alongside > the host app's plugins? Or is there another Rails "best practice" > approach that I haven't found yet? > > Any help greatly appreciated. > > Thanks > Tristan -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
