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=26814>. 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=26814 empty includesfile in fileset includes all files in dir Summary: empty includesfile in fileset includes all files in dir Product: Ant Version: 1.6.1beta1 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'm using an automated process (an XSLT transformation) to generate a file list that is used in a later task to create a fileset. The problem comes when there are no files to be added to the fileset. In that case, the includesfile is empty. Intuitively, I expected that the following fileset definition would include no files when tutorial-1-graphics.txt is empty (0 bytes). <fileset includesfile="c:\work\xml\test\ant\tutorial-1-graphics.txt" dir="/pubs/clementine/Images"/> Instead, what happens is that the fileset contains *all* the files in /pubs/clementine/images instead of no files. I can work around it by always writing at least one bogus file to the includesfile (zzz.zzz or something like that), but it seems to me that a fileset that uses an empty file to construct its include list ought to end up with no files in it. If I've missed something here, and this behavior is designed or intentional, perhaps someone would be good enough to point out the logic behind it. (I'm pretty new to Ant, so it's entirely possible that I just don't understand quite as well as I think I do.) Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
