DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20103>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20103 FileSet horrible performance when dir has huge number of subdirs ------- Additional Comments From [EMAIL PROTECTED] 2003-06-04 14:04 ------- True, when a fileset is used by a task to perform an action such as ftp or copy, the fileset is "scanned" through a class called DirectoryScanner. DirectoryScanner is looking at all files below the root directory of the fileset. 2 possible courses of action : 1) add support for FileList in tasks accepting FileSet this is a lot of work. In principle it is not a risky approach, but all tasks having to do with <fileset> would be impacted. 2) FileSets are explored by tasks such as <copy/> or <ftp/> through a utility class called DirectoryScanner. This one can be changed, so that if no wildcards are present in the include patterns, and the FileSet does not contain selectors, instead of recursively listing the root directory to match each file or directory against includes, excludes and selectors, the included files would be simply checked against exclude patterns if any. In the case that an included file is actually a directory, this one would be scanned. Please comment my suggestions. Antoine
