Hi Bill,
We are currently extending fileset to enable add something to existing
fileset. So your copy with two filesets could be rewritten into our concept
as:
<copy
todir="${project.source.root}\${application.architecture.serviceinterface.bi
n.directory}">
<fileset refid="common.files" redefmode="append">
<includes name="**.foo" />
</fileset>
</copy>
Unfortunatelly this is not currently in CVS yet, so if you like this
approach you have to wait some time...
Martin
----- Original Message -----
From: "William E Caputo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 13, 2004 5:00 AM
Subject: [nant-dev] FileSetCollection and the copy task questions
> Hi All,
>
> I am making sure I am not missing anything. I would like to use the copy
> task with multiple filesets like so:
>
> <copy
>
todir="${project.source.root}\${application.architecture.serviceinterface.bi
n.directory}">
> <fileset refid="common.files" />
> <fileset basedir="${other.files.dir}">
> <includes name="**.foo" />
> </fileset>
> </copy>
>
> The advantage of being able to do this is to be better able to factor out
> duplication (without having to duplicate otherwise identical copy tasks,
> that could eventually get separated in the build file).
>
> So, realizing that it wasn't there, I set out to add it, and I want to get
> some feedback first. Here are my assumptions/questions that I want
> confirmed/answered:
>
> 1) Should I use BuildElementArray or BuildElementCollection
> 2) There doesn't appear to be a FileSetCollection is that correct?
> 3) If so, is there any big issue that has prevented the creation of one
> (i.e. has someone tried?) or is it that it just hasn't been needed yet?
> 4) The CopyTask currently accesses a single FileSet, assuming a
> FileSetCollection existed, it appears that factoring the code that
> accesses this single fileset into a method called in a loop iterating
> across the fileset collection will provide the desired result -- anyone
> see any reason why not?
>
> Assuming I haven't missed anything, this looks like a relatively small
> change, that would result in a generally useful type (i.e.
> FileSetCollection) and the multi-fileset copy task. If this seems useful
> (and we get time to make the change) I will submit it back, if the nant
> team finds it useful.
>
> Thoughts?
>
> 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
