SVN project management tool usage

Record svn installation and use in eclipse for easy reference

1.1 What is svn?

SVN (Subversion) is a version management tool that has risen in recent years. In current open source projects (J2EE), almost 95% of projects use SVN. The original intention of the Subversion project is to replace CVS, the most popular version control software in the open source community at that time. There are many improvements based on the functions of CVS, and it can also better solve some shortcomings of the CVS system.

1.2 What is version control

Version control (Revisioncontrol) is a standard practice for maintaining engineering blueprints, which can track the process of engineering blueprints from birth to finalization. A system that records changes in the content of several files for future revisions to a specific version.

1.3 How to use svn

svn is based on client/server model:

2 svn server installation and configuration

2.1 Two server installation packages

2.1.1 Official installation package

Official website:http://subversion.apache.org/

Download: http://subversion.apache.org/download.cgi

2.1.2 Graphical server

The svn server with graphical operation interface developed by volunteers, it is suitable for ordinary software developers.

Download address: https://www.visualsvn.com/downloads/

3.2 Install the graphical server

View the program menu:

Looking at the service, VisualSVN started successfully:

3.3 Create a warehouse

After the svn server is created, a warehouse needs to be created, and the files to be version controlled are stored in the warehouse.

Go to VisualSVN server manager via the start menu:

Choose a file storage method:

Create an empty repository:

The warehouse was created successfully:

The warehouse address is https://ip address or computer name/svn/warehouse name

3.2 Create a project directory

To store development project code, documents, etc. in the warehouse, you need to create a project directory.

Created successfully:

Trunk: The main body of the project development code, which is in an active state from the beginning of the project until the current one, from which the latest source code of the project and almost all change history information can be obtained.

branch: A copy of the code separated from a certain point of the trunk. Usually, major bugs can be modified here without affecting the trunk, or experimental development, and custom function development. If the branch serves its intended purpose, it can usually be merged (Mgerge) into the trunk.

tag: used to indicate the status of a certain point of trunk and branch to represent a certain stable state of the project, usually the final release state.

Copy the svn address: