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=40516>.
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=40516


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
            Summary|<Availiable> should be able |Need a condition to check
                   |to handle nested filesets   |whether a fileset has
                   |                            |contents
   Target Milestone|---                         |1.7




------- Additional Comments From [EMAIL PROTECTED]  2006-09-15 14:37 -------
Filesets, by definition, are composed only of available files.  This doesn't
quite make sense.  However, in Ant 1.7 (I see you have reported this against
beta1), you can do this:

<waitfor>
  <resourcecount when="gt" count="0">
    <fileset dir="foo" includes="**/*.building" />
  </resourcecount>
</waitfor>

As far as I can tell this should satisfy your needs and since it works in the
version against which you made the report I am calling it invalid.  I am
changing the summary to be generic to your _needs_ rather than your proposed
solution.  Don't feel bad, because <available> does a lot, and sometimes it's
natural for people to think it should do -everything- and request enhancements
to this condition/task when another way already exists (see bug 22227).  That
said, given the resolution of this issue it seems you should have asked on
user@ant.apache.org first.

br,
Matt

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to