SVN environment Setup and use

SVN Server side: http://subversion.apache.org/packages.html

SVN client: http://sourceforge.net/projects/tortoisesvn/files/1.8.12/Application/

Note: The SVN server-side version must be greater than or equal to the SVN client version, otherwise The following error is reported: SVN checkout expects the file system format to be between "1" and "6"; Find format "7"

1. Create a root directory that is used to store all SVN factory information (each factory equals one project)

2. Open the Command Line window and start svn-->svnserve-d-R F:\DevRepository\Subversion

At this point, the SVN server side is already started. (Open a new command line window input "Netstat-na" SVN server-side default listening 3690 port)

But if the first command-line window is closed, the server stops. For Linux, a direct background boot is required. For window, background startup is useless, so it needs to be added to the window's service

Enter (run as Administrator) in the Command Line window SC create svnservice binpath= "D:\soft\common\Subversion\bin\svnserve.exe--service-r f:\ Devrepository\subversion "start= Auto depend= Tcpip. "D:\soft\common\Subversion\bin\svnserve.exe" represents the SVN installation directory under Svnserve.exe; "F:\DevRepository\Subversion" represents the root directory (defined by itself)

Svnservice is now available in the Windows service

Create a factory (project) in the SVN root directory (F:\DevRepository\Subversion)

First WAY command: svnadmin create F:\DevRepository\Subversion\Demo

The second graphical way:

The same directories are created in the previous two ways

Open the svnserve.conf. config file, change "# anon-access = read" to "anon-access = write" for anonymous users to read and write operations

Select a project to import the demo in this factory,

Svn://localhost/demo localhost is the name of the hostname Demo that was created under the SVN root directory

Import succeeded

Now let's assume that 01 and 22 users check out the code separately.

01 User checked out item (new folder for "01")

02 Users also check out the project

All right, you are done now!

For frequently used updates, the submitted action is not

Problems with the SVN use process:

After two developers have modified a file together and commit a conflict
1. Update the code before modifying it
2, the project manager when assigning tasks need to be independent to consider (for different developers to allocate different modules for development, so as to avoid conflict)

SVN permissions

passwd file

Authz file

Eclipse uses SVN

Plugin Address: http://subclipse.tigris.org/update_1.10.x

Show SVN repository view

Input Svn://localhost/demo

Then click Finish to complete, check out the project after

SVN environment Setup and use