Therefore, after building the code base, you must first set the svn:ignore attribute, and then provide the developer with the use, to avoid the development of the wrong version of the content will not be submitted to the SVN code base.
If you want to ignore files that already exist in the repository, you need to remove them from the SVN server before doing the following. Note: The newly created code base can directly ignore the files that you do not want SVN to manage by directly following the method below. But the actual content should not be submitted to the SVN code base. In this way, SVN will consider these directories and files in the local working directory to be new files, and also to version management. Compiling the source code of the Maven project will generate the target directory. Usually, the compiled products such as binary files and packages should not be placed on the SVN for version management.Īfter the SVN code base is created, after updating the code to the local and importing it into the Eclipse project, it will generate. should be uploaded for version management. Adding or modifying the SVN attribute needs to be submitted first, and then the local directory is updated to take effect.įor the SVN code base, only the source code, resource files, etc. The SVN attribute is the same as the source file. The svn:ignore attribute is used to set which directories or files in the local working directory are not used for version management, so SVN ignores them when adding or modifying these contents locally.
0 kommentar(er)
