ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31005] New: - When a filter throws a BuildException, no indication is given as to which file failed
Date Wed, 01 Sep 2004 22:21:21 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31005>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31005

When a filter throws a BuildException, no indication is given as to which file failed

           Summary: When a filter throws a BuildException, no indication is
                    given as to which file failed
           Product: Ant
           Version: 1.6.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: sxcoll2@yahoo.com


When a filter chain is being executed, say in a <copy> task, I would like to 
know what file on which the filter was executing against when the filter throws 
a BuildException.  Currently, 1.6.1 does not display this information.  Also, 
if it does throw an exception, that file in the <copy> destination directory 
should not be created so that on the second invocation of the <copy> the file 
does get copied otherwise to the user, it appears that the <copy> completed 
successfully because the zero length file still gets created.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message