----- Original Message -----
From: "Martin Aliger" <[EMAIL PROTECTED]>
To: "! nant" <[EMAIL PROTECTED]>
Sent: Wednesday, October 27, 2004 3:47 PM
Subject: [nant-dev] extending pre-defined fileset
> Hi all,
>
> some time ago, we had a discussion about fileset merging, subtracting and
> other operations.
>
> Maybe alot simpler schema will be better. What about this one? :
>
> <fileset id="docassemblies">
> ...
> </fileset>
> <if test="...">
> <fileset id="docassemblies">
> <include-fileset refid="docassemblies"/>
> <include name="..."/>
> </fileset>
>
>
> Just two things will be need to do for this (both easy enough):
> - implement include-fileset
> - allow <fileset> (type) definitions in contained blocks (like
> <if>,<foreach>,...)
We could just go for a nested fileset element after all. I'm implementing
something similar for a type called <path> or <pathset> (similar to the Ant
<path> element). Meaning :
<fileset id="...">
<fileset refid="...." />
<include name="..." />
</fileset>
But that might ofcourse cause problems for tasks where the relative path of
the files is determined (relative to the base directory of the fileset). For
some (most?) tasks, it makes more sense to support multiple toplevel
filesets.
> btw: includes->include but includesList->includesfile? IMHO "includefile"
or
> "include-file" would be better. But I'm not native English speaker so
maybe
> it is ok :-)
That was done to match Ant. Which is, as always, not really a goal by
itself, but I'm very bad at coming up with names, so I trust the Ant devs
more ...
Gert
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
