On Wed, 9 Mar 2005, Matt Benson <[EMAIL PROTECTED]> wrote:
> public interface FileCollection {
> public (String or File?)[] getFiles();
> }
maybe even Resource[]? That would capture ZipFileSet in a clean way
as well.
> I think it is sufficient to require the type selector's use to
> restrict to files or directories, if not overly friendly.
I agree.
> Set operations are fine; the referenced bug (5035) includes talk of
> nested FileSets. FileCollection unions, intersections and
> differences achieve the main spirit of the request in 5035; however
> we need to have some facility for adding additional restrictions (in
> the form of exclude patterns and selectors) to an existing
> FileCollection.
<union>, <intersect>, <difference> and <restrict>, maybe.
> I think the set operations should be implemented as FileCollections
> rather than tasks, for use inline.
+1
> I suppose we could have a "limit" FileCollection that applies
> exclusions and selectors to a single nested FileCollection.
Don't let me chose a name, please 8-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
