I'm trying to create a Rails Engine for Rails 3 and I'm having a similar problem. To test a Rails Engine plugin, you have to embed a full Rails application inside of the plugin's test folder. There are a couple of old tricks for loading the plugin into the embedded Rails app, for testing: http://www.justinball.com/2009/06/16/testing-rails-engine-gems/ Those tricks don't work any more, and it would really help me to be able to load the plugin using the config.plugin_paths setting.
Any other ideas for how to go about testing a Rails Engine plugin under Rails 3 would be much appreciated. On Jan 13, 7:54 pm, Sam Granieri <[email protected]> wrote: > I'm currently working on a rails app that separates open-source > plugins and company specific plugins into two folders, /vendor/plugins > and /vendor/shared_plugins by adding /vendor/shared_plugins to > config.plugin_paths . The initial refactoring of > pluginshttp://github.com/rails/rails/commit/82b9b151ffde44305d67744c0bfd9bb5... > will take config.plugin_paths away. Can it be brought back? -- 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.
