Gert
If you want to delete a directory or file that doesn't exist, then this
should just be considered a successful execution of the task, shouldn't it
be ?
yep. And it will work that way for filesets I think.
Certainly if there's currently no means to check if a directory (or file)
actually
Hi Ian,
If you want to delete a directory or file that doesn't exist, then this
should just be considered a successful execution of the task, shouldn't
it
be ?
yep. And it will work that way for filesets I think.
Ok, I'll update the Delete task to do the same.
Certainly if
Title: NScript: Tool to run .NET sourcefiles like script files
http://www.codeproject.com/useritems/nscript.asp
A VBScript that lets you run simple console-ish .NET sourcefiles in a script-like manner. Like Nant, it uses the .NET framework compiler (doesn't require VS.NET), and then runs
Recently got yet-another fresh checkout from CVS and ran
into a few problems which then raises a few questions
The root .build file successfully compiles everything, but the
unit tests dont make it. Now
that Im typing this, that behavior strikes me as even stranger, because
when
Brian,
The VS.Net files are just there for editing (and
debugging). I try to keep them in sync with the build files, but they are not
thereto build the project.
The nightly builds runfrom the
"nightly.build" filevia Draco.Netfroma new anon
cvscheckout. It basically runs a full release
Hi Gerry,
responses inline
- Original Message -
From: Gerry Shaw [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 5:39 PM
Subject: Re: [nant-dev] Delete task behaviour
What happens if you have directory foo that you want
Thanks, Scott Ill dig into
the metabuild and get myself sorted.
I can assume then that Draco
isnt getting what Im getting, then? (This is with nant
package, but Im getting the same with the default in debug.)
test:
[echo]
Running unit tests with just built version of NAnt.
[exec]
Yeah, I've seen this (time/date
failures)posted before. It doesn't show up in my builds, or the nightly
one, but people are seeing it consistently. If you can track this done it would
be very helpful :)
On a related note, we really need to beef up the
unit tests. That is definitely
Okay, I apparently lied. I can in-fact see this in
my builds. I took off my special blinders. :)
I just ran the nightly build (but it isn't night
you say, yeah... yeah) to check for this message. I've setup the nightly build
(which will only occur if there were changes since the last
Brian Deacon wrote:
(and Ian, I thought you were gonna commit my vast improvement on
the echo task?)
Committed ! thanks.
Ian
---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and
On Wednesday, February 19, 2003, at 10:17 AM,
[EMAIL PROTECTED] wrote:
Gerry:
delete dir=f00/
The delete task will not raise an error and your directory foo will
not
exist.
I liked the feature that Gert suggested, but I see Gerry's point. What
about this:
Add an attribute, say
I have to disagree on this point. Not necessarily in this case but in
general. Adding more options is not better than working out what the
right way to do it is.
A good article, thanks for the link. IMO, It depends on the type of
application -- and the type of user. It also depends on how those
Hi Gerry,
I agree with you that adding an attribute like 'ignore_failures' should definitely
avoided.
Please have a look at my updates to the DeleteTask that I sent earlier today.
These updates correspond with how Ant currently works, and no, I'm not saying that we
should do everything
13 matches
Mail list logo
