The "failonempty" attribute only causes the task to fail if the ENTIRE
fileset is empty. I want to fail the task if ANY single <include> is empty.
Can this be done? If not, would this be an acceptable enhancement request
for a future version?
I have some tasks where I explicitly list the files being included. When I
mistype a file name, the task can appear to run succesfully, even though one
of its required inputs is missing. This makes debugging harder. If I had a
"failonanyempty" or "mustexist" attribute at the <fileset> level (or
"failonemtpy" on the individual <include> level), finding and fixing these
types of errors would be easier.
This message and any attachments are intended only for the use of the
addressee and may contain information that is privileged and confidential.
If the reader of the message is not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
dissemination of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by e-mail
and delete the message and any attachments from your system.
Get latest updates about Open Source Projects, Conferences and News.