Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration existed Subclipse projects #203

Open
FoxyBOA opened this issue Nov 20, 2021 · 2 comments
Open

Migration existed Subclipse projects #203

FoxyBOA opened this issue Nov 20, 2021 · 2 comments

Comments

@FoxyBOA
Copy link

FoxyBOA commented Nov 20, 2021

Does Subclipse allow relink existed Subversive projects?
Yes. Please see stackoverflow workaround https://stackoverflow.com/q/70044376/19347

I have a bunch of SVN projected checked out via Subversive. I would like migrate to Sublicpse, but I don't see an option how to relink existed SVN projects (SVNKit 1.8.14) to Subclipse (SVNKit 1.10.1.10793).

I open existed project with Subclipse based Eclipse, configure SVN server, but Team->Share popup menu doesn't have option "Share..." that allows to relink detached SVN projects.

Any ideas?

P.S. Some details are here

@markphip
Copy link
Contributor

I am not aware of any solutions to this problem. It is really an Eclipse problem. The issue is that when you connect your project to a Team provider (Subversive), Eclipse stores this somewhere so that it can then connect up the plugin for that Team provider to your project.

The problem is that when you no longer have this plugin installed you are now left in the situation are in where there are no options on the Team menu. If the Subversive plugin was still installed then there would be a Disconnect option available to break the link between your project and Subversive. Once that was done the Team > Share would be available again so you connect with Subclipse.

Ideally, Eclipse would provide some way for you to disconnect or otherwise handle it when the associated Team provider is not present.

@FoxyBOA
Copy link
Author

FoxyBOA commented Nov 21, 2021

The workaround is

  1. Delete all your projects that have this problem, but in the delete dialog, do not delete the project contents!
  2. Select File -> Import -> Existing projects into Workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants