My cache implementation deals with SourceValidity instead of lastModified(), which allows caching for sources where lastModified isn't available (e.g. a CVS directory, or a tagged CVS source which can go back in time if the tag is moved). Also, I added a "directories-only" parameter which automatically filters regular files (it can be needlessly expensive to get infos on them and later discard them in the pipeline).
But my implementation started from the 2.0 DirectoryGenerator which hasn't all the fancy sort stuff. So I think a merge is actually what's needed.
Be my guest. ;-) If I can be of any help, just let me know.
And while we're at refactoring, what do you think of having separate regexps for directories and files ? This would be really useful since their respective naming rules are totally different. E.g. if I want only .xml files, the regexp has to be "^[^.]*$|\.xml$", which looks quite ugly when the file regexp would simply be "\.xml$".
How do you plan to express that in the component configuration? I'm afraid it might start being overcomplicated...
Ciao,
-- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Now blogging at: http://blogs.cocoondev.org/gianugo/)
