The hard journey to install the SVN plugin in eclipse

We write Java program people know Eclipse, also installed some plug-ins, such as the use of Android development need to install ADT, if the code submitted we may need to install Git and SVN plug-ins, but this plugin I have heard before, but has not been installed, So the difficulty of the installation should be small, I would not use this plug-in, but just to a new company (each company's system is not the same, this must be adapted), he submitted the code, need to leader to review a bit (generally this is the case, Unless you are the first one to work on this project, you will be sure to familiarize yourself with the code first and then modify the commit. Boss See can be submitted. But installing the SVN plugin in eclipse is really a hassle. Encounter a lot of problems, so here's a summary:

The first thing to declare is that we didn't use the SVN plug-in in eclipse before, when we committed the code, we committed it using the client, but after installing the SVN plugin in eclipse, we were able to manipulate it directly in eclipse. It is also convenient to see which items have been modified in the project view of Eclipse. Here's a look at the problems I encountered during the installation process:

First I installed the SVN client in the computer is svn1.8.8 64-bit , at the beginning I installed the SVN plugin in eclipse, so I found a plug-in package from the Internet (offline installation):site-1.8.8. The installation is ready. Feel successful, first we use the client locally to pull the project down. Then import into Eclipse, and then we right-click the project:

Select Team->share Project and then associate the SVN:

Select SVN and click Next to select the SVN address:

If this is the first time, select Create a new SVN repository address:

Here to fill in the SVN address, but here to note that we can not fill in the full address, URL fill only to the branch name, do not include the project name, such as SVN on the truck branch under a project Androiddemo:

We are using the client SVN update when the address: http://10.10.10.10/XXX/truck/androiddemo, a local general new Androiddemo folder, Then checkout.

But here we have imported the local Androiddemo project into eclipse, so the URL here should be: Http://10.10.10.10/XXX/truck is OK, such as:

We can see that the local project address will automatically become Http://10.10.10.10/XXX/truck/AndroidDemo, of course, the module name can be modified, but we have written in the previous should be Http://10.10.10.10/XXX /truck/, otherwise this side will have the problem, then the association on the OK.

Then we can do the commit and update of the code in eclipse:

You can also do code comparison:

This is a success. But I have shown above that I was successful, and did not say that I encountered the problem:

Here's a look at the problem:

First question: Version issue

As we said above, my client installs svn1.8.8 64-bit, and then the plug-in package installed in Eclipse is site-1.8.8. At first, I thought it was the right version, but if the version is incorrect, you'll be prompted with an error when adding SVN-related items to eclipse. The SVN version of your client is inconsistent with the version of the SVN plugin installed in Eclipse, in fact, the last to know that their two version numbers are inconsistent and corresponding. Finally, search for the two versions of the corresponding case, found a version of the corresponding situation:

The version of the local client installation is: Tortoisesvn-1.7.5.22551-x64, the version here is 1.7.5

: Http://pan.baidu.com/s/1pJ0pxof

The version of the plug-in package installed in Eclipse is: site-1.8.5

: http://pan.baidu.com/s/1k0Tmm

OK, now see, these two version numbers are inconsistent. The question about this version has been going on for half a day. Hey...

So in the future when we install this plugin, we must pay attention to the version of the corresponding relationship, and then install, but if we worry about the version of the problem, we can choose not to install the client version, but only install the SVN plugin in Eclipse, Then we just need to create a new project in Eclipse Androiddemo (equivalent to create a new Androiddemo folder locally) and then associate it so that we don't have to be bothered by these two versions of the problem. But there is a problem, the problem is that I have encountered, do not know whether other people have encountered, is the update code in Eclipse is always not full, and eclipse easy to flash back. There is no client stability, so I still choose to install the local client.

A second question

After SVN is associated with local eclipse, it is frustrating to find that the local cannot be commit/update, but instead prompts you to upgrade (working copy). The problem is really breaking me up, because the problem above has made me sick of it. Hey...

But I accidentally restart the computer after the good (really did not expect it ...) )

After two of the above issues are resolved, I can submit and update the code in Eclipse and locally, happy ~ ~

Summarize:

About SVN, I generally did not install plug-ins in the eclipse operation, are operating on the client, the original thought to install a plug-in is very simple, did not expect that there will be so many problems.

In fact, the biggest problem here is that we install the SVN version of the client and the SVN plugin version in Eclipse is inconsistent.

Of course, if you want to avoid this problem we can choose to install only the SVN plug-in package in Eclipse.

The hard journey to install the SVN plugin in eclipse