Again, a fileset only works on *existing* files, so flattening it would
give a set of filenames that don't exist (yet?).
It makes sense for <foreach> to support a mapper though.
Erik
Duane Mattos wrote:
> I guess I'd like to create a new fileset from an old one. I'd like to use
> foreach on the new fileset (or the 'right' side of the map, no longer care about
> the left). I don't think the perforce tasks support wildcards, so I thought I
> could iterate through a fileset, but I need to flatten the filenames.
>
> dM
>
> -----Original Message-----
> From: Erik Hatcher [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 24, 2002 3:45 PM
> To: Ant Users List
> Subject: Re: applying mappers to fileset
>
>
> No. That doesn't really make sense in a general sense, at least to me.
> A fileset is a set of existing files, so mapping them doesn't preserve
> that meaning.
>
> Mappers are associated directly with several tasks, such as <copy>.
>
> What do you have in mind specifically?
>
> Erik
>
>
>
> Duane Mattos wrote:
>
>>Can I apply a mapper (flatten in my case) to an arbitrary fileset? How do I
>
> do
>
>>so?
>>
>>thanks!
>>
>>dM
>>
>>--
>>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>>
>>
>>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
