Return-Path: Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Delivered-To: mailing list dev@ant.apache.org Received: (qmail 83959 invoked from network); 20 Mar 2003 03:03:55 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 20 Mar 2003 03:03:55 -0000 Received: (qmail 365 invoked by uid 50); 20 Mar 2003 03:05:46 -0000 Date: 20 Mar 2003 03:05:46 -0000 Message-ID: <20030320030546.364.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@ant.apache.org Cc: Subject: DO NOT REPLY [Bug 18128] - Dependset srcfileset does not handle absolute path X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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=18128 Dependset srcfileset does not handle absolute path ------- Additional Comments From mxlehma@qwest.com 2003-03-20 03:05 ------- Then why does the following work for srcfilelist: I would think that the handling for the directory would be done the same way. The advantage of using srcfileset over srcfilelist is that if the file doesn't exist, then it is not used. I have been able to do what I need with the srcfilelist, but I am forced to create several additional targets to conditionally generate a filelist with only those files that exist. The danger of srcfilelist and srcfileset handling the absolute filenames differently, is that without running ant in verbose mode and specifically testing a change to the src file, you would never know that the dependency was not there.