SVN / Subversion 1.7 and Eclipse Subversive & JavaHL

Question

I have just upgraded to TortoiseSVN 1.6.99, Build 21709, (Subversion 1.7.0, -dev). I am having problem in my Eclipse Subversive 0.7.9.I20100512-1900 & JavaHL 1.6.15. Have tried to update my Eclipse plugins. Anyone have an solution?

Error at Eclipse:

Share project was failed. Unsupported working copy format svn: The path 'XXX' appears to be part of a Subversion 1.7 or greater working copy. Please upgrade your Subversion client to use this working copy.

Answer 1

Bear in mind that Subversive doesn't communicate with your working copy directly; it is only an interface for Eclipse. The communication runs through an SVN connector such as SVNKit or JavaHL. This is the software you should update to resolve your problem.

In my case I'm using SVNKit, which can be updated like so:

1. Make sure Eclipse's update sites are pointing to Polarion's recommendations. Here's what my update sites look like:
2. You'll need the latest version of Subversive SVN Connectors, so make sure the Subversive update site is enabled and let Eclipse check for updates through Help, Check for updates.
   • Check Eclipse's Installation Details to confirm that you've got Subversive SVN Connectors version 2.3.0.I20120413-1700 or later. To do so, go to Help, About, then click "Installation details".
   • If you haven't gotten a new version, you might need to uninstall the old one, and grab the new one from the Subversive update site.
3. Now you may update SVNKit. Select Help, Install new software to bring up the software installation window.
4. Select the latest SVNKit (as of this writing, 1.7.4) and install it.
5. Restart Eclipse.

If Subversive is using the wrong connector after restarting Eclipse, select the right newest one from the preferences screen (under Preferences, select Team, SVN then click the tab "SVN Connectors").

Answer 2

You are aware of the Subversion 1.7 state? It is currently a beta-2 state and not intended for production? Furthermore it couldn't work with the working copy, cause the working copy format of 1.7 has changed and it will not upgrade your working copy automatically. If you like to use 1.7-beta-2 you have to use the JavaHL version of Subversion 1.7-beta-2 instead of 1.6.X. The above mentioned is also true for TortoiseSVN, cause the version you mentioned is a BETA! (as explained on the TortoiseSVN site.