Re: Why does the implementation keep track of filesNotIncluded, dirsNotIncluded?

Stefan Bodewig wrote: Is there any way you can make the pattern more specific or can the test output files really be everywhere in you source tree? Thanks for the reply, Stefan! A more specific inclusion pattern indeed helps, and we'll use that solution. bryan -

Why does the implementation keep track of filesNotIncluded, dirsNotIncluded?

I ran what I thought was a fairly simple Ant target, to remove unwanted JUnit output from my build tree: I found that running this target uses memory proportional to the size of my entire tree, rather than using memory proportional to the number of JUnit