Yeah, I actually started to write support for match collection (checking that includes resulted in file selection) into the fileset, but gave up when I didn't come up with an elegant solution. I tried working with the existing fileset code but think it probably needs to be completely rewritten to support this.
It is a pretty important feature, and also fairly isolated, if anyone wants to take on the challenge. :) ----- Original Message ----- From: "Gordon Weakliem" <[EMAIL PROTECTED]> To: "Lalonde, Paul" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Ian MacLean" <[EMAIL PROTECTED]> Cc: "Nant Developers" <[EMAIL PROTECTED]> Sent: Friday, February 21, 2003 10:04 AM Subject: Re: [nant-dev] Delete task patch > There was some discussion of this about a month ago, IIRC it turned out to not be easy to do. This is actually a good FAQ item, I took the liberty of adding it to the FAQ. > > -----Original Message----- > > This discussion does bring up another interesting point though, which is > more general than just on the delete task: When using a fileset the > <include> elements may match no files. That's all good and fine, and > correct in many cases, but it leads to unexpected behaviour in the case > of typographic errors. A warning when an <include> matches no file, > perhaps with a matching failure flag, could go a long way to addressing > both the delete issue and the more general fileset usage. > > Paul ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
