I just counted the number of active eclipse workspace I have: Eight! I’m sure there are other developers which even have more than eight? Eclipse maintains many settings inside the workspace .metadata folder (see my post on CodeWarrior Tool Tip #1: Improve performance by cleaning house in the Eclipse workspace). The question is: how can I copy or transfer my carefully balanced workspace settings to another workspace?
The solution is not that obvious. But is straight forward once I knew about it: I can export and import the workspace settings. For this I select the menu File > Export and select General > Preferences:
Exporting Workspace Preferences
The next dialog gives me the opportunity to select what to export (I usually select ‘Export all’) and to which file (which is a normal text file):
Exporting Preferences Details
Applying the preferences (or settings) to another workspace just works the other way round: I use the menu File > Import > General > Preferences. Simple like that🙂.
Hint: I use File > Export > General > Preferences as well to have a backup of my preferences (in case eclipse might screw up my workspace). Or to store the settings in a version control system.
Happy Preferencing🙂
Pingback: Managing recent workspaces | MCU on Eclipse
Thanks for that awesome posting. It saved MUCH time🙂
LikeLike
Pingback: Eclipse global preferences | MCU on Eclipse
Pingback: Customize my Workspace Perspectives | MCU on Eclipse
Thanks for the tip.
BTW, the given link of “CodeWarrior Tool Tip #1…” doesn’t work anymore. You moved it to http://blogs.freescale.com/2011/11/10/codewarrior-tool-tip-1-improve-performance-by-cleaning-house-in-the-eclipse-workspace/
HTH.
LikeLike
Thanks for reporting the broken link. Fixed now🙂.
LikeLike
Pingback: Spaces vs. Tabs in Eclipse | MCU on Eclipse
Thanks, this is helpful. I hope to share preferences across a team; putting the preferences file in a version control system should help me do that.
LikeLike
As the preference file is in XML format, it is easy to store and distribute it using a version control system. Only a heads up: I have found that some plugins might not export their settings (for whatever reasons, a bug to me). So always good to verify things. Apart of that, I store the settings as well in my SVN as a ‘backup’: because it happens from time to time that my workspace .metadata gets corrupted. That way I can easily re-apply my workspace settings again.
LikeLike
Thanks for your advice. The only problem I see is that the team may forget to import the preferences when creating new workspaces.
LikeLike
Yes, this is a problem. But have a look at https://mcuoneclipse.wordpress.com/2012/04/06/eclipse-global-preferences/ which proposes a way to apply settings for every new workspace. There is another way to control the workspace perspectives too: https://mcuoneclipse.wordpress.com/2012/07/14/customize-my-workspace-perspectives/
LikeLike
Thanks again. The trouble with Eclipse is that it is very complicated!
LikeLike
Yes, at the beginning things are a little bit overwhelming. The good news is that after a learning curve I cannot imagine any more to use another IDE. So I hope as well that my posts might help finding a way through everything.
LikeLike
Pingback: Eclipse Workspace Tips | MCU on Eclipse
This one tip alone saves me endless frustration! I archive our work to the repository after changes throughout the day. It is often necessary to export a past version and build a new work space (I don’t want to risk any corruption or error in the production system), then import the older project code (I don’t archive the eclipse system). But I always had to go through and manually put all the settings back into eclipse. What a mess! Now I just save the settings with the archive and it is always there for a new work space. Thank you.
LikeLike
Pingback: Constructing a Classroom IDE with Eclipse for ARM | MCU on Eclipse
Pingback: Toolchain: KSDK 1.2.0 with Eclipse 4.4 (Luna) and GNU ARM Plugin | Centaurian
This is not a good solution. It does not copy the appearance settings, keyboard shortcuts or snippets.
LikeLike