I think about that by myself :)
You said that a Resource could could give Input/OutputStream.
So it would be possible just to add another Cache implementiation based
on that.
I thought of implementing the ResourceSelector interface additionally ...
Jan
> -Ursprüngliche Nachricht-
> Von: Matt Benson [mailto:[EMAIL PROTECTED]
> Gesendet am: Dienstag, 24. Mai 2005 17:43
> An: Ant Developers List
> Betreff: ResourceCollections WAS Re: AW: cvs commit:
> ant/src/testcases/org/apache/tools/ant/types/opti onal/depend
> ClassFileSetTest.java
>
>
> --- [EMAIL PROTECTED] wrote:h
> > >
> >
> src/resources/org/apache/tools/ant/types/resources/selectors
> >
> > Do you mean, we have to rewrite our file-selectors?
> >
>
> Any fileselector continues to work with fileset/dirset
> as well as . Most fileselectors should still
> be relevant as resourceselectors, and in those cases
> it might be nice to delegate file selection to the
> corresponding resourceselector, just to decrease the
> number of places where an implementation of a check
> exists. I didn't attempt to create a resource version
> of because a) I don't understand it :) and
> b) I wasn't sure how to handle the properties file
> approach that exists w/ the file version. It is
> probably translatable, but I hoped maybe you could do
> it :) or help me to.
>
> -Matt
>
> > Jan
> >
>
>
>
> __
> Yahoo! Mail Mobile
> Take Yahoo! Mail with you! Check email on your mobile phone.
> http://mobile.yahoo.com/learn/mail
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>