Re: FileCollections WAS FileSets with optional basedir and absolute paths for includes

2005-03-11 Thread Peter Reilly
Stefan Bodewig wrote: As for relative vs. absolute this is a problem anyway. Mappers need relative names in many places, so if the iterator returned Files instead of Strings they'd need a way to get back to the relative name - and if it was String many tasks will need a way to get the basedir to re

Re: FileCollections WAS FileSets with optional basedir and absolute paths for includes

2005-03-11 Thread Stefan Bodewig
On Thu, 10 Mar 2005, Matt Benson <[EMAIL PROTECTED]> wrote: > --- Stefan Bodewig <[EMAIL PROTECTED]> wrote: >> Just to be clear, I'm talking about the existing >> oata.types.Resource here which already gets used by zip family of >> tasks. > > Yeah, not a bad idea. Do you think we are setting > o

Re: FileCollections WAS FileSets with optional basedir and absolute paths for includes

2005-03-10 Thread Matt Benson
--- Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Thu, 10 Mar 2005, Stefan Bodewig > <[EMAIL PROTECTED]> wrote: > > > Resource instead of File could be even better. > > Just to be clear, I'm talking about the existing > oata.types.Resource > here which already gets used by zip family of tasks.

Re: FileCollections WAS FileSets with optional basedir and absolute paths for includes

2005-03-10 Thread Stefan Bodewig
On Thu, 10 Mar 2005, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > Resource instead of File could be even better. Just to be clear, I'm talking about the existing oata.types.Resource here which already gets used by zip family of tasks. We may even add a getInputStream method to it ... Stefan ---

Re: FileCollections WAS FileSets with optional basedir and absolute paths for includes

2005-03-10 Thread Peter Reilly
An iterator would be nice. It would be useful to deal with very large number of files. Currently tasks like store all the files and maps in memory and then processes the files. This causes problems like OOM exceptions when dealing with large directories. A url or resource would also be nice instre

Re: FileCollections WAS FileSets with optional basedir and absolute paths for includes

2005-03-10 Thread Stefan Bodewig
On Wed, 9 Mar 2005, Matt Benson <[EMAIL PROTECTED]> wrote: > Right now I am leaning toward: > > public interface oata.types.FileCollection { > public Iterator iterator();//of Files > } Iterator works for me, but so would an array. We do have some cases where we only want to check whether a

RE: FileCollections WAS FileSets with optional basedir and absolute paths for includes

2005-03-09 Thread Matt Benson
--- Dominique Devienne <[EMAIL PROTECTED]> wrote: > > From: Matt Benson [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 09, 2005 4:13 PM > > To: Ant Developers List > > Subject: FileCollections WAS FileSets with > optional basedir and > absolute > > paths for includes > > > > Right now I am

RE: FileCollections WAS FileSets with optional basedir and absolute paths for includes

2005-03-09 Thread Dominique Devienne
> From: Matt Benson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 09, 2005 4:13 PM > To: Ant Developers List > Subject: FileCollections WAS FileSets with optional basedir and absolute > paths for includes > > Right now I am leaning toward: > > public interface oata.types.FileCollection { >