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=21759>. 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=21759 Failonerror should apply to directory copy. Summary: Failonerror should apply to directory copy. Product: Ant Version: 1.5.3 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When copying a directory using the copy task and a fileset, the build fails if the source directory does not exist. The failonerror attribute of the copy task does not work when copying a fileset which I believe does not make much sense. The documentation states that there is no meaning in the failonerror in case of using a fileset. Why not? If the fileset definition has problems, it makes sense to honor the failonerror value and to continue without performing the copy operation. At least in my case it does: I have to add some pictures for my javadocs from another subproject in my version control system (MKS). If the subproject is not included in my local materialization, I would like to continue without those pictures, because the javadocs are a. not essential and b. still usable. However, I cannot do this using ant. I set the failonerror property on the javadoc task. OK! I set the failonerror property on the copy task. Not OK! Is there another solution? Regards, Uli. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
