static member may be the easiest way forward.
Thanks
for you input Henry, it has been very useful.
Cheers,
Bill
-Original Message-From: Price, Henry
[mailto:[EMAIL PROTECTED]Sent: 13 May 2004
17:39To: Bill Martin;
'[EMAIL PROTECTED]'Subject: RE: [Nant-users] I
/manual/CoreTasks/java.html
Regards,
Martin
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
Subject: RE: [Nant-users] Interim state on a build between SUCCEEDED and
FAILED
Date: Thu, 13 May 2004 16:56:03 +0100
MIME-Version: 1.0
X-Originating-IP: [62.189
Title: RE: [Nant-users] Interim state on a build between SUCCEEDED and FAILED
Thanks
for that Henry,
It's
not quite what I want to do, but it has given me a couple of ideas. Your
idea of defining a property is good, I can do this inside my task and add or
modify the property o
Title: RE: [Nant-users] Interim state on a build between SUCCEEDED and FAILED
Henry/BillA)Put all of your mission critical
tasks up front in some sort of clean or init target specifying
failonerror="true" for all critical tasks
B)introduce the concept of task dependencies to
lat
I have written a custom task to perform a scan on a VS project file when the
build is executed to ensure the project complies with standards (it checks
that option explicit is set in a VB project for example and checks for files
in the archive that aren't part of the project.)
The problem I have i
