Martin Aliger:
>We are currently extending fileset to enable add something to existing
>fileset.

Yes, that would work for the example I sent (I thought about your recent 
posts after I sent my email). After sending, I realized that the 
refactoring I was doing also needed to do something like this (for which I 
don't think the redefining modification is enough):

<copy todir="\foo\one">
   <fileset refid="common.files" />
   <fileset refid="less.common.files" />
 </copy>

<copy todir="\foo\two">
   <fileset refid="common.files" />
   <fileset refid="other.common.files" />
 </copy>

<copy todir="\foo\two">
   <fileset refid="other.common.files" />
   <fileset refid="less.common.files" />
 </copy>

(etc)

In short, I have somewhere between 3 and 5 discrete blocks of assemblies 
that have to be copied to something like 10 different directories, in 
various combinations that make it impossible (as far as I can see) to get 
rid of the redundancy with single filesets.

Unless, the new mods support multiple refid's? (that would remove the need 
for multiple fileets -- at least in my case). E.g.:

<copy todir="\foo\two">
   <fileset refid="common.files" refid="other.common.files" mode="append" 
/>
 </copy>

or perhaps:

<copy todir="\foo\two" mode="append" >
   <fileset>
        <refid>common.files</refid>
        <refid>other.common.files</refid>
   </fileset>
 </copy>

If not (and I am assuming not, from what I've seen so far), I would be 
interested in people's opinions on the  preferred way -- multiple refid's 
or multiple filesets (or both, or something else)?

Best,
Bill

William E. Caputo
ThoughtWorks, Inc.
http://www.williamcaputo.com
--------
idia ktesis, koine chresis





-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to