> Maybe something like this might work out better for you. Use "svn ls -R" > and find the directories you have to checkout:
> svn ls -R http://myserver/svn/proj | grep "/trunk/$" Thanks, David. I did bring up using 'svn list' in my original post and grep'ing for trunk, but that took 4 times as long as the actual checkouts that need to be performed. And even a 1.6 server won't improve that. I've started the ball rolling on an SVN server upgrade. Without that, I don't see any feasible non-brittle solution. With that, I'm thinking that iterating N levels deep with "--depth immediates" will be performant. I'm not sure how Ant does at emulating 'find . -type d' command... @Bob Archer: Yes, I've had dozens of SVN sandboxes on-disk at once both inside and outside of Eclipse. They too were various versions of projects. I strongly suspect our situation is different. This one project has different branches and tags at different levels. In fact, our production support team will be mainly responsible for the proj/top2/deploy/** subtree, including tagging, whereas the other trees will be managed by us product developers. I suspect there will be at least 5 different "sets" of trunk/tag/branch trees, updated at different times, some perhaps with different naming conventions (for branches and tags).
