Anderson, Kelly wrote:
for testing this target:
You could certainly do that with something like
The problem is when you get to things that invoke other nant targets,
i.e. dependencies, call tasks, and nant tasks. Procedural programming
languages rely on link-time h
I'm not talking so much about testing Nant itself, I understand how
that's done.
I'm talking about testing small portions of the script you are
developing.
If there's no good way of doing it, I can accept that, but I wonder if a
family of tasks could be created something along these lines:
for
- Original Message -
From: "Asis Yuval" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, September 13, 2005 4:04 PM
Subject: [Nant-users] Error lines not written in the log file
> Hello Everybody
>
>
> I am using task for recording NAnt output to log-file, on
> failure i am sending
> an E-m
Hello
Everybody
I am using
task for recording NAnt output to log-file, on failure i am
sending
an E-mail with
attachment with this log-file , the problem is that the significant lines
are not appearing
in the log,
the NAnt print them after closing the log-file and sending the
mail.
