You have to rely on this patch [1] (unlreleased, pending for 2.5.20 this weekend) and instruct your users to vendor the gem.
The alternative is to ensure that the load-path includes the file containing your Capistrano recipes, and include a generator to copy this into your users' projects, or to generate a file that loads something from your Gem. If you tell me which project it is, I can probably better assist you - it's hard to know the best thing to suggest when I don't even know what you're working on? [1] http://github.com/capistrano/capistrano/commit/ee1d6bd272b8e66378f9b1ce7db75ee49c98093d - Lee On 8 October 2010 14:46, Nadal <[email protected]> wrote: > I have a rails2 plugin which has a capistrano task. That file resides > at ~/myplugin/recipes/ . > > I am converting this plugin into a gem which should work with rails3. > This is what I did. > > I created recipes file inside the lib/myplugin directory. So my file > looks like > > ~/dev/myplugin/lib/myplugin/recipe.rb > > And added following line to my deploy.rb > > require 'myplugin/recipe' > > However capistrano is failing with message: no such file to load -- > myplugin/recipe. > > > How do I convert a rails2 plugin into a rails3 gem with capistrano > recipe? > > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to [email protected] > * To unsubscribe from this group, send email to > [email protected]<capistrano%[email protected]>For > more options, visit this group at > http://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" 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/capistrano?hl=en
