I'm in the process of implementing a parallel type task (similiar to the
existing Ant task).
I've pretty much got it working and was playing with it in our current build
file. The first thing I found was that properties that are declared within
a target are global in scope. Needless to say, t
these changes I would appreciate it.
Thanks -andy
X-OriginalArrivalTime: 19 Mar 2004 16:44:39.0636 (UTC)
FILETIME=[78A10140:01C40DD1]
Any,
I committed your fix to cvs, however I would advise you to upgrade to NUnit
2.x asap.
Gert
- Original Message -
From: "Andy Sipe" <[EM
We're in the process of upgrading to 0.84 from 0.81. I found what appears
to be a problem with the NUnit1 task. It no longer creates the test output
files. I tried several variants of the task and couldn't get it to function
correctly, so I took a look at the code.
It seems that the formatte
I've just started using the latest stable release (0.8.01) and I think there is a problem with the NUnit1 task. It appears to be ignoring the haltonerror and haltonfailure attributes. I looked at the code in NUnitTask.cs and I think I've found the problem. The way it is currently coded it throws
I noticed that the exec task always waits for the program to exit before moving on. We want to use NAnt as a driver for system level regression tests. For this we need to be able to start an application and move on to the next target before the application finishes.
Is there any reason that
