Easy way to move a project in Eclipse

Question

My projects change location, and I need to tell Eclipse. (I’m not the one who moves the project, it already exists in different folders. To work with another branch, I work in a different folder.) Today I just delete the project from Eclipse and import it from a new location.

But I have many projects, they often change their place, and the paths are very complicated. I would like it to be better in Eclipse.

For example:

J:\iteration234_abc\foo\bar\baz\iffle\dizzle\Project 

Only the root folders will change (iteration number and idenfier "abc"). After that there are many folders. Many folders have many subfolders with similar names, which allows you to find a folder with a graphical interface, taking a lot of time and very boring.

It would be so nice if I could just edit the path.

As you might have guessed: J-drive is a network drive provided by version control system. The way to report source control that I'm working on another iteration is to continue my work in another folder. The actual Eclipse workspace usually does not contain any projects.

Answer 1

I believe that in this case it is easier to have two different eclipse workspaces, each of which points to projects elsewhere.

Then you can simply use "File-> Switch Workspaces" to change all open projects at once.

Answer 2

Another option is to export the "Team Project Set". You get an XML file, for example:

 <?xml version="1.0" encoding="UTF-8"?> <psf version="2.0"> <provider id="org.tigris.subversion.subclipse.core.svnnature"> <project reference="0.9.3,https://xxx/trunk/com.image4j,com.image4j"/> <project reference="0.9.3,https://xxx/trunk/com.jacob,com.jacob"/> </provider> </psf> 

This is a file that can then be edited manually and then imported into an empty eclipse workspace.

Answer 3

Export the project in the "Project Sharing" format (mainly a mail file). And then reimport zip to the "new" location - all old fixed paths will be mapped to the new paths.

Answer 4

I do not understand why your source of control should lead to a change in the local project. Perhaps you should consider using SVN or another SCM, which does not require you to change the path at all.