If I was understanding the test2 scenario correctly,
i.e. test2 doesn't get deleted because it's not empty
until test3 is deleted for being empty, I *think* this
will work as expected in HEAD. I did some things in
there specifically to sort directories such that
children would be encountered bef
On 5/8/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
That's a good solution Matt. Gets rid of test3.
Thank you to both of you :)
FTR, I'm a strong proponent of generating all build output into a
single dir (I use the build/ dir myself), and never anywhere in the
Agreed. Unfortunatel
On 5/8/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
OK, now I'm pretty confident everything's working as expected.
*chuckle* so now that we're on even footing...;)
Desired outcome:
> files test/something.ini, test/test1/test2/another.ini deleted
> dirs test3 and test2 deleted as both a
On 5/8/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
Liz, I'm still not 100% sure I understand your use case now ;-)
Would you mind providing a simplified sample listing of the files in
your directory before , the XML snippet for the tag
with its nested elements you're using, and which fil
On 5/8/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
In your first example, your empty dirs are implicitly included, and
and later not excluded, so will get rid of them.
In your second example, your include pattern prevent the empty dirs
from being selected, because they don't match your p
rther discussion. Is there a reason
that includeemptydirs acts this way with includes? Or is it something that
was overlooked?
Thanks!
Liz Burke-Scovill
--
Imagination is intelligence having fun...
[EMAIL PROTECTED]
