How do you make eclipse use an existing svn working copy?

Question

I've got a working copy checked out with svn; furthermore, I've created a new project in Eclipse that has the root of the working copy as the project's location. I want to be able to do stuff like compare versions from Eclipse. I have Subclipse 1.4.8, but that doesn't seem to give me what I want. Am I doing something wrong?

Answer 1

When you open a versioned project (i.e., a project in SVN working copy) in Eclipse, that was never previously used with Subclipse, you need to perform these steps:

1. Right-click the project in Project Explorer.
2. Select Team | Share Project.
3. At this point Subclipse will tell you that "The project is already configured with SVN repository information". Click Next.

Subclipse automatically recognizes this project as versioned and all the features of the SVN plug-in should become available.

Answer 2

I have encountered a similar situation were existing projects would not get associated with the Subversive plugin. Unfortunately, none of the previous suggestions helped (renaming projects etc.). What has helped is removing projects from Eclipse by deleting them -- just the projects from Package Explorer and not the actual directories and files on disc (the deletion prompt has a special checkbox for that, which is unchecked by default) -- and reimporting the deleted projects as existing projects back.

Of course, as mentioned in some of the answers here, the relevant SVN repositories need to be registered with Eclipse before reimporting the projects. Otherwise, there would no repositories to re-associate the projects with.

Answer 3

This worked for me: 1) Go to the 'SVN Repository Exploring' perspective and add a folder somewhere above your working copy 2) Close and open the Eclipse projects.

This should then be enough to get them recognized by Subclipse.

Answer 4

You can right click on the root node of your project and select: Team / Share project

Then you choose SVN, let the default settings and it should work fine!

Answer 5

I had the same issue and here are the details of the fix.

My Eclipse is "Helios Service Release 1".

I had an SVN checkout on my filesystem, I went to New Java Project, unchecked Use default location, chose the location, went to next step, chose the source folder and said Finish.

The project came up with no disk icon on it. As per few forum posts, right-clicked on the project, went to Team > Share Project, chose SVN, clicked Next, and the option was only to share the files to the SVN Repository for the first time.

I said Cancel, and the option is to make changes to the SVN plug-in settings. Went to Window menu, chose Preferences, browsed Team> SVN. Chose the SVN Connector tab, changed the SVNKit 1.2.3 to SVNKit 1.3.5 and said OK.

Then, right clicked on the project, said Team> SVN, on the next screen, chose the option Use Project Settings and clicked Finish. The disk button came to the project and the SVN URL got displayed on it.

Answer 6

I am answering this after a long time of the question being asked. I ended up here because I was facing the same problem.

My solution was to create an empty .svn folder at the root folder of the project (in the latest version of svn client tortoise all meta-data is at the root folder). Then did an eclipse refresh and voila it did the trick. I am running subclipse core - 1.8.4.

Answer 7

One step that seemed to work for me, that no one has explicitly mentioned yet: I closed and then re-opened the project. I tried the "rename" trick, above, and that didn't work, but perhaps the poster of that answer also closed the project - they didn't detail exactly what steps they went thru to rename it. (I found you don't have to close the project to rename it, but perhaps they did.)

< /rob>

Answer 8

In my case, I couldn't use an existing copy because I checked out the code using a newer version of Subversion on the command-line and Subclipse 1.4 couldn't recognize it. Upgrading and going through the improved "Share Project" menu resolved the problem.

I got this tip from the forums here:

http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2380064

Answer 9

i have an svn working copy that also is a project in eclipse. after installing the subclipse plugin i had the same problem, the working copy was not recognized as such.

i just managed by chance to get it recognized as an svn working copy by renaming the project in question and then renaming it back to its old name. not very nice, but it did the trick :-)

Answer 10

It will definitively not work if you use a different version of svn to checkout, that the one that is supported by Eclipse. I had this problem as I used svn 1.6 to checkout but I had an older eclipse version that had only 1.5. Subclipse has its own build-in svn client (Actually, in two flavors if I am not mistaken).

Check that the subclipse version matches the svn client that you used to checkout. You can check the plugin version number for subclipse (Help -> About -> Click on subversion logo) and match it against svn --version

Answer 11

I guess this is not possible with Subclipse as it's given in its documentation that, you can only import an existing svn-managed folder under one condition, according to the doc:

"The only requirement is that your working copy has to also be a valid Eclipse project."

So, if you have a working copy that is not a complete eclipse project, Subclipse will not connect it to SVN.

Answer 12

Add the repository to your list of repositories in subclipse by choosing Window->Show View->Other... and choose SVN->SVN Repositories. Put in all the necessary info to connect to the repository.

Next, right click the repository and choose "checkout". If the project doesn't already have an eclipse .project file, you can create a new project from the source. If it already has a .project file, it will import that .project and use that as your eclipse project locally.

Answer 13

There is an option when creating a new project, to use an existing source directory:

New project/ new Java Project / Create project from existing source.

Use that, tell it where your source lives, and it should automatically detect if it's a SVN working copy.