Sorry - I think I misphrased the question - the problem IS reproducing now - the issue is that the child tasks are not filtered by the CALLER task's filters. Which is the reverse of my earlier question, and I guess your first answer applies to my real question - and that it is by design.. So essentially, you cannot have re-usable sub functions, you need to define separate functions for each filter.
On a related note, can you over-ride tasks for only certain filters? It did not seem to work, but just thought I would ask to make sure anway. It seems to override the filters for the entire task, instead of overriding the task for the specified filter. On Feb 14, 7:22 am, Jamis Buck <[EMAIL PROTECTED]> wrote: > Ah, I read it backwards. I thought you were saying that B and C call > A, but it is the other way around. Yes, that should work as you expect. > > - Jamis > > On Feb 14, 2008, at 8:20 AM, mzorova wrote: > > > > > Never mind - this was not working last night, but it is now - must be > > lack of sleep and some mistake I made yesterday. (btw, the question > > should have had run "echo blah" instead of puts) > > > On Feb 14, 6:24 am, mzorova <[EMAIL PROTECTED]> wrote: > >> The role filters are not applied on child tasks - only the :except > >> and :only seem to be applied - is this a bug or by design? > > >> example: > > >> task :A do > >> puts "A" > >> B > >> C > >> end > > >> task :B, :roles => :web do > >> puts "B" > >> end > > >> task :C, :roles => :app do > >> puts "C" > >> end > > >> running cap A > > >> puts A B C on ALL servers - it should > > >> A on every server > >> B on web only > >> C on app only > > > > > > smime.p7s > 3KDownload --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
