Re: [nant-dev] types merging

2004-01-20 Thread Jaroslaw Kowalski
Perhaps it would be more efficient to hold off on the patch until more people have provided feedback, and until we've decided it in more detail. I'd hate to see your efforts go to waste ... My 0.02 PLN: 1. I don't think merging can be done in a generic way (neither on xml level nor at the

Re: [nant-dev] types merging

2004-01-20 Thread Martin Aliger
3. Maybe we should start by implementing it the simple way: Make includes and excludes support filesets (both referenced and nested): fileset basedir=dir.a includes file=aaa.txt / includes fileset=r1 / includes fileset basedir=dir.b

Re: [nant-dev] types merging

2004-01-20 Thread Jaroslaw Kowalski
BTW. Can you have this? (both reference a named fileset and re-define it ?) fileset id=aaa refid=aaa includes name=*.* / /fileset Jarek --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development

Re: [nant-dev] types merging

2004-01-20 Thread Martin Aliger
BTW. Can you have this? (both reference a named fileset and re-define it ?) fileset id=aaa refid=aaa includes name=*.* / /fileset Jarek Not in current implementation. I dont like it much - using both id and refid is little opaque... Better to introduce what you suggest in previous

Re: [nant-dev] types merging

2004-01-20 Thread Jaroslaw Kowalski
Not in current implementation. I dont like it much - using both id and refid is little opaque... Better to introduce what you suggest in previous mail: fileset id=aaa includes refid=aaa / includes name=*.* / /fileset To be more readable, I would: 1. Make fileset fail on attempts

Re: [nant-dev] types merging

2004-01-20 Thread Jaroslaw Kowalski
I think this is sufficient in 99.9% scenarios so if we don't find merge be useful we could always implement this [I have it in some state already] Should such implementation include even excludes from referenced fileset? I suggest the following evaluation semantics: fileset includes

Re: [nant-dev] types merging

2004-01-20 Thread Jaroslaw Kowalski
I think this is sufficient in 99.9% scenarios so if we don't find merge be useful we could always implement this [I have it in some state already] Should such implementation include even excludes from referenced fileset? I suggest the following evaluation semantics: fileset includes

Re: [nant-dev] types merging

2004-01-20 Thread Jaroslaw Kowalski
Sorry for my previous example. The resulting fileset should be empty because files cannot be both xxx.* and AAA.*. Jarek the resulting fileset is (in terms of the set algebra, + means union, - means difference) L1 + L2 - (L3 - L4) so (because we're excluding almost every file but AAA.*)

Re: [nant-dev] types merging

2004-01-19 Thread Gert Driesen
-dev] types merging Here it is. I also react to Gert's notes inline... Also is attached mine test build script. Martin - Original Message - From: Ian MacLean [EMAIL PROTECTED] What do you think? Should I prepare patch for it? sure. I'd like to see it. Ian - Original

Re: [nant-dev] types merging

2004-01-16 Thread Ian MacLean
What do you think? Should I prepare patch for it? sure. I'd like to see it. Ian Martin --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching