the specific failure reason / stack trace
/ etc in this notification.
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 28, 2004 4:29 PM
To: Breen, Patrick; [EMAIL PROTECTED]
Subject: Re: [Nant-users] Access to failure reason text in onfailure target
Is there any property that contains the text of the failure reason (ie,
the summary info that Nant reports when a build fails) at the time an
onfailure target is invoked? If not, is there a way to get at this
information via script?
Thanks -
Patrick
Here's what we did to work around this:
- set the values of properties that define information about the test to
be run (essentially, we are setting the parameters to a worker target)
- invoke each unit test by re-invoking nant with the unittest target and
failonerror set to false. Example:
Check out http://nunit2report.sourceforge.net/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tim
Dallmann
Sent: Thursday, January 08, 2004 5:13 PM
To: [EMAIL PROTECTED]
Subject: [Nant-users] XSLT Stylesheet for task output
Hi There,
I was just wonde
Invoke devenv.com instead of devenv.exe (both should be in the same
directory). It will pipe output to the stdout which will then be
captured by Nant.
Patrick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Dagg
Sent: Friday, December 12, 2003 6:47
FWIW - this is how I changed things to implement an "execute only once"
idiom within a target:
--
In version 0.8.4 when a target is defined with a dependency that calls
another target with the same dependency, the target is executed a second
time. In version 0.8.3, the target was only executed once. Which is the
proper / desired behavior? The build scripts we have were counting on
the 0.8.3 b
Ran into the same problem the other day. My resolution: use Nunit
2.1.4 and rebuild Nant with this new version of Nunit. Worked like a
charm.
Patrick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 8:3
Title: Message
I'm using
with a timeout setting (0.8.3 final) but it doesn't seem to
kill the program when the timeout expires. I've created a simple example
below that runs cmd.exe and waits for input (ie, it runs for an arbitrary
length of time) - and the process is never killed.
If I
