"MidnightJava" wrote:
To do this, check out the code from your SCM server into some location, presumably on your share drive. Then open Eclipse and create an empty workspace somewhere. From the file menu, select Import->Existing Projects into the workspace (under the General category). Uncheck the "Copy project into workspace" button, assuming you don't want to have two copies of your files. Now the projects themselves will be on the share drive, but your workspace will exist where you created it. You'll just have a .metadata folde there, which eclipse uses to lock your workspace, keep track of what you're doing, and maintain workspace preferences. Any changes you make to your projects will occur on the server, since that's where the files are. Whenever you switch workspaces, you must refresh all resources, to make Eclipse aware of changes you made from the other workspace.
This is exactly what I am looking for! I already have all of my code automatically synced to cloud backup, so corruption isn't really a concern, and I'm the only one who works with the code, so concurrent edits/conflicts aren't either, but I might get it all into SVN anyway just for redundancy, branching, and the ability to rollback changes if necessary.
Thanks for all the help folks, and sorry for the mini-hijack!