Hello
1) Multiple files: Added a project level variable called
nant.project.failure, such that a you can allow a task or
group of tasks
to complete regardless of failure using failonerror=false, and then
afterwards check the value of nant.project.failure to determine if a
failure
]
Subject: Re: [nant-dev] 2 small changes to consider
Hello
1) Multiple files: Added a project level variable called
nant.project.failure, such that a you can allow a task or
group of tasks
to complete regardless of failure using failonerror=false, and
then afterwards check the value
the local build meister fix it for next time.
Clayton
-Original Message-
From: Randy Regnier [mailto:[EMAIL PROTECTED]
Sent: February 27, 2004 7:42 AM
To: 'Martin Aliger'; 'Nicklas Norling'; 'Gert Driesen';
[EMAIL PROTECTED]
Subject: RE: [nant-dev] 2 small changes to consider
Our
This patch adds wildcard support to file::exists(). Basically it uses
DirectoryScanner to find matching files.
Is it ok to commit it ?
Jarek
fileexists.patch
Description: Binary data
Subject: Re: PATCH: file::exists() wildcard support, WAS: Re: [nant-dev] 2
small changes to consider
Is there any reason that you don't always use the scanner?
if (file.IndexOf(*) != -1 || file.IndexOf(?) != -1) {
...
} else
return File.Exists(Project.GetFullPath(file));
Less code paths
Yeah, I'm sure we all go back and forward on this issue. Performance is
important, and we should strive towards it, but I have found that
sometimes
what seems like a performance tweak turns out to not work out as I expect.
I'm sure the scanner is slower than file.exists, but in this case I
- Original Message -
From: Hemry, Jeff [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, February 26, 2004 8:48 PM
Subject: [nant-dev] 2 small changes to consider
Hi all,
Here are 2 small changes put in place for our specific needs that may be
beneficial to the whole
2) Availabletask: modified to allow for wildcards, such that it would be
acceptable to determine if c:\temp\*.txt is available.
I guess you could accomplish this using the foreach task, perhaps not a
pretty way to do it, but possible ...
We are actually thinking about deprecating the
