SVN external Reference (svn:externals) handles common code for similar systems

We often encounter a scenario in which we have two systems, two systems using the same set of frameworks. If we use two sets of procedures

To do, when we modify this public framework, the other is the old version, it is easy to cause confusion.

The external use of SVN is to deal with this situation.

We have a system A, a system B. We extract their common files, as System C, by a separate SVN version management repository. Then A and B systems refer to C respectively. In this way, both A and B systems can be synchronized to the latest C code, whether modified or acquired.

Here's how to set up an external reference directory:

This way, in addition to this, the project all the code will be submitted to the main URL, in addition to the "Common Code" directory will be submitted to the external reference directory you set.

It is important to note that the main version and the common version of the directory can not be duplicated, what does it mean?

Suppose the home directory is a,a with a B directory. You can no longer create a reference directory for B.

However, if there is no C directory in B, you can create the C directory as an external reference directory.

SVN external Reference (svn:externals) handles common code for similar systems