I wrote: > I have one repository with two projects. Project A externals in a couple > directories from Project B (a library). But the tag I need to pull in from > Project B did not have a Windows build, only a target (Linux derivative) > build, so I have a third external defined to pull in a Windows build of > the Project B library to the place it would go if it were there in the > first place. This worked in version 1.6, but now gives an error in 1.7 and > does not pull in the file.
I searched the archives (Sorry, I guess I should have done that sooner) and came up with this: http://svn.haxx.se/dev/archive-2011-10/0377.shtml Like the poster in that thread, this issue is preventing many on my team from upgrading to SVN 1.7. In that thread, the claim was made in response that this worked "by accident" in version 1.6, but I do not see any reason why this might be the case. Is this actually the case? Is this something that can be fixed, or will file externals always be limited to be placed only within folders belonging directly to the current working copy? Regardless of whether it was originally an intentional feature, it is very useful when it works. And, directory externals do NOT have this limitation, so it seems quite arbitrary to the end user, even if the underlying implementation is very different between file and directory externals.
