Owen Rogers wrote:
i was just doing some profiling of our build and i noticed thatCheck out the cascade attribute of the <call> task, http://nant.sourceforge.net/nightly/latest/help/tasks/call.html .
certain tasks were getting executed twice. we use a mixture of call
tasks and depend attributes in our build file. it seems that if a
target is *call*ed its *depend*encies are executed -- even if they
have been previously executed on a different *call* stack. i'm not
too sure if this is a feature or a bug or if it is just a nant best
practice not to mix the two (calls and depends). i've attached a
I believe this will help control things the way you want, but I'm not sure. "Cascade," while reasonable as the attribute name, isn't much help in the documentation, but I think it really means "if true, then first invoke the dependent tasks whether or not they've been invoked already, if false, only invoke them if they haven't been invoked yet."
I think the term "best practices" is really overused. In this case, there is no best; there are legitimate reasons for both.
Gary
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
