2

After a recent upgrade to eclipse Juno, I have a problem with eclipse no longer being able to remember certain settings across restarts and workspace switches. Things like which perspectives were open, certain settings like "[x] Open Dashboard" (spring ide) seem to revert to their factory settings whenever eclipse is restarted.

I use Ubuntu and for historical reasons I maintain my eclipse installation in /opt/eclipse. The installation is owned by root, and apart from some issues with upgrades, this has not actually been a problem - until the Juno release.

I have tried chown -R myself:myself on the eclipse installation directory, and I have verified that all files are indeed editable by my own user. Still, the perspectives seem to reset.

Is there any other place where eclipse stores this information, which might still be owned by root?

user1283068
  • 1,694
  • 4
  • 15
  • 25

3 Answers3

9

Information about perspectives is stored in
< workspace>\.metadata\.plugins\org.eclipse.e4.workbench\workbench.xmi

Keep this file backed up if you use complicated customized perspectives.

P.S. It's also useful to know that deleting this file may solve the problem when Eclipse doesn't start (see also here)

Community
  • 1
  • 1
sberezin
  • 3,266
  • 23
  • 28
1

That information is kept in the .metadata directory in each workspace root directory.

Chris Gerken
  • 16,221
  • 6
  • 44
  • 59
  • I just checked, and under .metadata/.plugins there are some subfolders that, for some reason, are owned by root. This must be why I was experiencing these problems. Thanks for your help! – user1283068 Jul 06 '12 at 11:49
  • Unfortunately this is not the case here on my system. Not nowadays. – Regis May Aug 26 '21 at 08:13
0

Two solutions:

  1. MENU -> File -> Switch workspace -> Other -> Copy Settings of

    • Workbench Layout
    • Working Sets

  2. Copy/backup and replace following folder to new created Workspace.

    • [workspace]/.metadata/.plugins/org.eclipse.ui.workbench/
    • [workspace]/.metadata/.plugins/org.eclipse.core.runtime/.settings/

Personally I prefer (2).

The above answer is credited to @Ischin, in the following reference...

Community
  • 1
  • 1
crazycliffy
  • 146
  • 1
  • 3