Ian MacLean wrote:
note that this has been through some revision - originally
dependencies were not executed by default and there was a "force"
attribute if you did want to execute them. It was subsequently decided
that executing dependencies was the more common - less surprising
behaviour. It
alizing
>
> compile:
>
> [echo] compiling with debug = false
>
> compile:
>
> [echo] compiling with debug = true
>
> BUILD SUCCEEDED
>
> Hope this helps,
>
> Gert
>
>
>
> From: [EMA
compile:
[echo] compiling with debug = true
BUILD SUCCEEDED
Hope this helps,
Gert
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Troy
LaurinSent: vrijdag 13 mei 2005 7:26To: Ian
MacLeanCc: Gary Feldman; NAnt UsersSubject: Re:
[Nant-users] mix
On 5/13/05, Ian MacLean <[EMAIL PROTECTED]> wrote:
Gary Feldman wrote:> Check out the cascade attribute of the task,> http://nant.sourceforge.net/nightly/latest/help/tasks/call.html
.>Thats exactly right - maybe another doc fix is required. cascade="true"means execute dependencies and is the defa
Gary Feldman wrote:
Owen Rogers wrote:
i was just doing some profiling of our build and i noticed that
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
Owen Rogers wrote:
i was just doing some profiling of our build and i noticed that
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 pre
i was just doing some profiling of our build and i noticed that
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
