It's usually best to let Eclipse copy the workspaces for you.
I usually keep my projects external to the workspace
You should avoid having the same project appear in different workspaces .
But if the project is completely contained within the workspace then its likely OK.
I have different workspace sets based on the release.
For example
[dvavra@fred 2019-09]$ ls -l /home/dvavra/workspaces/2019-09
total 40K
drwxr-xr-x. 5 dvavra dvavra 4.0K Aug 28 17:26 deepnets
drwxrwxr-x. 11 dvavra dvavra 4.0K Dec 31 12:45 Default
[dvavra@fred 2019-09]$ ls -l /home/dvavra/workspaces/2019-06
total 968K
drwxr-xr-x. 4 dvavra dvavra 4.0K Aug 10 06:17 arduino
drwxr-xr-x. 5 dvavra dvavra 4.0K Aug 28 17:26 deepnets
drwxr-xr-x. 9 dvavra dvavra 4.0K Aug 10 06:36 default
I use rsync to migrate a workspace from one release set to another.
Unfortunately, there are absolute paths within a lot of the files pointing to the old location.
Mostly within the .metadata directory.
Requires a massive edit to fix. ("sed -i" can help here)
A similar problem occurs when renaming a workspace.
There are files with references to the old name.
There really is no easy way to do this.
And I often find I can't remember the steps I used the last time.
This is where backups come in handy.
When you screw up you can go back to a set point.
It's annoying enough that I procrastinate several releases before upgrading.
[Updated on: Wed, 01 January 2020 11:50] by Moderator
Home
