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-05-21 18:00 ------- Now that I am using <filelist> as a workaround to <fileset>, I have run into another problem. I want to copy the <filelist> to another directory, but the <copy> task doesn't take a <filelist> type. <target name="cachejars"> <copy todir=${CACHE_BASE_ENG_DIR}"> <filelist refid="jarlist"/> </copy> </target> build.xml:91: The <copy> task doesn't support the nested "filelist" element. I have found it confusing that there is a <filelist> and <fileset>. I think <fileset> should be modified to encompass <filelist>, i.e. <fileset> should be able to specify an explicitly named list of files either as absolute paths (dir=null) or relative to dir. <fileset> already lets you specify explicit files relative to <dir>, but the performance is horrible. Once <fileset> is enhanced, you should be able to deprecate <filelist>, which would make ant simpler to understand for new users. I know I was confused over when to use <fileset> and when to use <filelist>
