Hmm. Good point. Merging two filesets into third one...
In fact I'd added also this (but don't think it will be needed. Maybe it
will be!):
<copy todir="\foo\one">
<fileset>
<includeFileset refid="common.files" />
<includeFileset refid="less.common.files" />
</fileset>
</copy>
or simmilar (and same result in this case):
<copy todir="\foo\two">
<fileset refid="common.files" redefmode="append">
<includeFileset refid="other.common.files" />
</fileset>
</copy>
What do you think? And others? I'm still not sure how about xml merge of
such filesets
Martin
----- Original Message -----
From: "William E Caputo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 13, 2004 1:48 PM
Subject: Re: [nant-dev] FileSetCollection and the copy task questions
> 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
>
-------------------------------------------------------
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
