Recursive validation is supported with Subversion1.5, as this thread illustrates .
In "Version Control with Subversion", the book mentions the svn checkout , svn update , svn switch and svn export commands as a recursion option in external repositories, but:
- If an external value is specified for a particular revision, no amount of "
update " will change a single file in it, although the external repo has new versions. - an update should always start with the parent repo, and not directly from the subrepo:
Be careful, however, that you do not arbitrarily modify your external working copy in subtle ways that cause problems.
For example, while the definition of an external source may indicate that the external working copy should be stored with a specific revision number, if you run svn update directly in the external working copy, Subversion will be required, and now your external working copy will be out of sync with his announcement in the main working copy.
So perhaps one of these two cases applies here.
OP Carsten Report:
He is working now.
I set the external support for the root node of an external project (let's say the ' lib ' project).
In my specific project (project " A "), the external was defined in a subfolder of " lib " (ie myLocalFolder > lib/someFolder ).
This, apparently, is the reason that subversion does not recurs external to lib ; just looked inside ' someFolder ', did not find external definitions there, so he did not check someFolder/externalLib .
Now in ' lib ' I have changed the definitions of externals so that they are defined inside the folder that I refer to in ' A '; Now works like a charm!