Eclipse "Share Project" manually?

What actually happens with the file system when you run the Subclipse Share Project in an Eclipse project that has been extracted from Subversion from the outside? All .svn folders are already installed. I get an error when I try to share the project correctly, and I do not want to delete and re-check projects from the SVN repository browser.

+6
eclipse svn subclipse
source share
3 answers

I don’t know exactly what happens inside the eclipse, I believe that he does some funny things in the workspace's .metadata directory. However, I would recommend the following to get an eclipse in order to find out about the project svn settings:

  • Delete project from workspace (save “Delete project contents on disk” not installed)
  • File> Import ...> General> Existing Projects in the Workspace
  • Browse to the folder containing the source project (s) of interest.
  • Import projects into the workspace

This is similar to a side effect of the subtitle that notices subversion settings when importing “new” projects into your workspace.

+12
source share

The Share Project action is intended to fix the first version of the project, i.e. without metadata .svn. He will be upset if he sees .svn directories already there. As Rob wrote, the way to get this proven project in Eclipse is to use import capabilities.

+2
source share

I am not sure which version of Eclipse you are using or it will apply, since I use Subversive instead of Subclipse. When I use the share project function to transfer the project to svn, when I already have all the .svn directories, I get a choice like “Use current project settings” and then the eclipse automatically binds the svn project information to the integration command. You can spoil it if you try to enter various information.

+1
source share

All Articles