Question

Installed Eclipse Kepler, Subclipse 1.8, SVNKit. Several (not all) of my projects now have only "[]" instead of the usual path into the repo. I can't see any obvious relationship between those that still have a full rpo path and those that now have on "[]". The two solutions to similar problems mentioned here (though none were identical) do not work:

  • renaming the project, then renaming it back -> no change

  • disconnecting the project then using "share project" -> complains that there is no SVN metadata data in the root of the project (except that there is)

The two other solutions recommended, namely "reinstall everything" and/or "delete the project (retaining files) and re-import it into the workspace" I want to keep as absolute last resort.

The situation is complicated by the fact that the SVN info associated with the projects is old and needs upgrading. A disconnected project cannot be shared, because it there is no "upgrade" option (just "Apply patch" and "Share Project"). A connected project with a "[]" path cannot be upgraded because the option is greyed out, along with everything else on the "Team" menu except Commit, Create Patch, Apply Patch, Show Revision Graph, Add to Version Control, Revert and Disconnect.

A further difficulty is that some of the "[]" projects are newer than their repo versions, with changes I want to preserve. So discarding the local copies and checking out new ones is not an option, at least not for all affected projects.

So, what I specifically want is some way to re-connect those projects with a repo path of "[]" to their correct repo paths. Some explanation of what the heck happened would be a bonus :-)

Any suggestions gratefully received.

Was it helpful?

Solution

Based on all of the things you mentioned, I would guess that the working copy is not the right format. The current version of Subclipse is 1.10.x which would require a Subversion 1.8 working copy format. Team > Upgrade would be available to update it.

You said you have Subclipse 1.8.x installed, so that would requires a Subversion 1.7 working copy format. If the working copy is from a lower version then you could upgrade it, but if the working copy is from Subversion 1.8, then it will not be able to read it.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top