http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1277
*** shadow/1277 Mon Apr 9 15:40:46 2001 --- shadow/1277.tmp.21867 Mon Apr 9 15:40:46 2001 *************** *** 0 **** --- 1,28 ---- + +============================================================================+ + | Apply fails when there are no input files | + +----------------------------------------------------------------------------+ + | Bug #: 1277 Product: Ant | + | Status: NEW Version: 1.3 | + | Resolution: Platform: Macintosh | + | Severity: Normal OS/Version: MacOS X | + | Priority: Component: Core tasks | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + There are many occasions where Apply might be used on an empty + fileset, and should not fail under that condition. + + In my case, I'm using Apply to run gcc on any source files that are newer + than their corresponding object files. I have four different file sets in my + apply command, any of which (or sometimes all) contain only up-to-date + files (a regex mapper is used to figure out which sources need to be + compiled). When this happens I get a "no input files" error and a result + code of 1. + + IMHO, apply should either 1) not return an error when a fileset is empty or + 2) provide a "failOnEmptyFileset" attribute.
