I think it is easy. <zip> already supports part of it with <zipfileset>.
<delete> will delete the original file. <copy> and others will copy or see
the files with new names. I just want to avoid copying a hundreds megabytes
of data just to lay them out correctly. It would help with <sync>. It would
also be possible to say that a client fileset is component1 and component2
client filesets.
- Alexey.
{ http://trelony.cjb.net/ } Alexey N. Solofnenko
Pleasant Hill, CA (GMT-8 usually)
-----Original Message-----
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 8:27 AM
To: [EMAIL PROTECTED]
Subject: Re: Any chance for fileset arithmetic?
On Tue, 29 Jul 2003, Alexey Solofnenko <[EMAIL PROTECTED]> wrote:
> I actually meant that mappers inside filesets would rename files
> in the filesets.
I'm still not sure I understand it.
> I need something like:
>
> <fileset id="client.fileset">
> <fileset dir="build/docs" prefix="wwwroot/docs"/>
Say you have build/docs/index.html.
Do you expect the invocation of DirectoryScanner#getIncludedFiles
to return "index.html" or "wwwroot/docs/index.html"?
What would you expect <delete> to do with that fileset? What would
you expect <zip> to do?
> Right now I have to execute <copy> every time I need a complex
> fileset.
By using <copy> you physically create a file structure, this is quite
different from the above.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
