Sounds good. I'm assuming tasks added with 'before' and 'after' would be added to a fifo stack?
- Mike On 5/5/07, Jamis Buck <[EMAIL PROTECTED]> wrote: > > > Thanks for raising this, Mike. I've been waiting (since before 1.0) > for this to become an issue, and it looks like the time has come. > > Here's what I'm thinking of hacking into cap2: > > before :update => :custom_task > after :deploy => :another_task > > Also > > before :update do > # ... > end > > And > > before "deploy:update" => ... > > Sound reasonable? > > - Jamis > > On May 3, 2007, at 1:20 AM, Mike Bailey wrote: > > > Hi all, > > > > some projects require that little bit of extra love to get them > > deployed. > > A task like :after_update in deploy.rb can be just the thing. > > > > But this will stomp on a task with the same name in a plugin (like > > 'deprec') > > Can anyone think of a way I can use before_ and after_ filters in > > deprec > > without them being stomped on by end users in their deploy.rb? > > > > BTW, I've fixed outstanding bugs in deprec but am waiting for > > rubyforge to > > fix my login issues. My account doesn't work anymore. Grrr. > > > > - Mike > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
