Several methods and usage details of configuring SVN in eclipse

This article also applies to MyEclipse.

I Download the subclipse plug-in in eclipse

Method 1: download the specific operation from the eclipse marketplace: open eclipse -- > help -- > eclipse marketplace -- > enter subclipse search -- > find subclipse and click Install

Method 2: download from install new software

Specific operations: open eclipse -- > help -- > install new software -- > click the Add button and enter the download address: http://subclipse.tigris.org/update_1.10.x , click OK

-->After checking subclipse and svnkit, you can go all the way to the end of next or agree (here, because I have installed it, next is gray)

Method 3: directly download the zip file of subclipse. Specific operation: Baidu search subclipse-site-1.10 X (depending on which version you want to install) - > after decompression, find the dropins folder in the eclipse directory, enter the dropins folder and create a new folder named SVN, copy the features and plugins folder to the SVN directory -- > Restart eclipse

2： Upload project to SVN server

1. In eclipse, call up the SVN repository view from show view

2. Right click the blank position in the SVN resource pool window and select the new resource pool location

3. Fill in the address of the server

4. The resource pool is imported successfully. The imported resource pool appears in the SVN resource pool view

5. Create a new project

6. Write the initial version of the project

7. Right click Project -- > team -- > share project

8. Select the repository type as SVN -- > and click next

9. Use existing repository locations

10. Use the project name as the folder name -- > click finish -- > and enter the user name and password (not everyone has this step)

11. Freely choose whether to open the synchronize view

12. Right click Project -- > team -- > submit

13. Freely choose whether to write log (recommended)

@H_ 502_ 202@

14. Click OK -- > to upload to the server successfully. At this time, the resource library will be refreshed, and the uploaded project will appear under the resource library

3： Download project from server to local

1. In the resource pool view, click the small triangle on the left of the resource pool, and all projects under the resource pool will appear

2. Select the project to download and right click -- > check out as

3. Freely choose whether to change the attribute (it is recommended to use the default) - > finish -- > Download succeeded

4： Update code from server

1. Right click the project -- > to synchronize with the resource library

2. Select to open the synchronize view

3. The server code different from the local code will be displayed in the synchronize view. Double click to view the comparison between the local code and the server code. The plus sign is the newly added file (there is no local code yet)

4. Switch the mode to incoming mode. The codes in this mode are updated by the server and need to be downloaded locally. Right click the file -- > team -- > to be updated

5. If the following symbol appears, it means that there is a conflict between the local code and the server code (that is, the local code changes the code without updating to the latest version; or someone uploads a new a.java code to the server during your code writing to a.java, resulting in a conflict between the codes)

5： Solutions to conflict situations

Conflict case 1: the server code is the same as your own code

This situation is complex. Generally, you can only save a copy of your own code locally, then directly update the server code, and then modify your logic on the new code.

Conflict situation 2: the server code is different from your own code

This is a common situation. You and other developers are changing the same file, but the development tasks are separate, so the changes are different. The solutions are as follows.

1. Double click the conflict file to enter the comparison view

2. Find the code block added on the server but not locally, select this code block, click the button in the upper right corner (as indicated by the arrow in the figure below) to copy the server code locally (the same operation is also performed in other places). If clicking the button is useless, close the comparison view and reopen it

The following figure shows the successful copying of server code to local code,

3. After copying the newly added codes on all servers to the local file, right-click the conflict file and select mark as merge. At this time, the file will disappear in the synchronize view, and the code of the file has successfully merged the local code and remote code together

The above is the whole content of this article. I hope it will help you in your study, and I hope you will support us a lot.