When you set the externals property, it does not copy files from the external repository to your working repository. Rather, it simply creates a “note” on where to extract these files in the future.
Thus, when creating a tag, svn does not bother to copy actual files that are linked externally. Instead, it simply copies the “note”. If you checked your tags/1.0.1 directory (or updates if it is already locally checked), you will notice that it correctly pulled out the corresponding external elements, even if these files did not exist in the working repository.
change
Ah, I finally saw the problem. You install external in the root directory, not in the trunk directory.
The best way to view svn is that it is just a file system, the whole idea of a chest, tags and branches is just conceptual ideas, and each directory is no different from the next.
Thus, when copying a trunk to the tag catalog, external properties are not transferred, since they are not part of the trunk catalog (they only talk about the delivery of external elements to the trunk). To solve the problem, you must remove the external properties from the root directory and add them to the trunk. The next time you create the tag, the external properties should be migrated.
Next command:
svn propget svn:externals file:
should be displayed:
file:
Dunes source share