Clean out Eclipse workspace metadata

Question

I use multiple workspaces with Eclipse  I recently noticed that some of my workspaces have a lot of cruft in them from software packages that I installed and then later removed  As far as I can tell  the situation is that many packages write stuff  sometimes a lot of stuff  to the  metadata folder for every workspace I open while the package was installed  When I removed a package  it seems to clean out the  metadata folder for the workspace that I happen to have open at the time  but all the other workspaces are left with orphaned metadata  Sometimes this metadata causes problems mdash often  errors while opening the workspace and sometimes instability   The only way I know to deal with this is to create a new workspace  import projects from the polluted workspace  reconstructing all my settings  a major pain  and then delete the old workspace  Is there an easier way to deal with this

User · Accepted Answer

There is no easy way to remove the  outdated  stuff from an existing workspace  Using the  clean  parameter will not really help  as many of the files you refer to are  free form data   only known to the plugins that are no longer available   Your best bet is to optimize the re-import  where I would like to point out the following    When creating a new workspace  you can already choose to have some settings being copied from the current to the new workspace  You can export the preferences of the current workspace  using the Export menu  and re-import them in the new workspace  There are lots of recommendations on the Internet to just copy the   old workspace   metadata  plugins org eclipse core runtime  settings folder from the old to the new workspace  This is surely the fastest way  but it may lead to weird behaviour  because some of your plugins may depend on these settings and on some of the mentioned  free form data  stored elsewhere   There are even people symlinking these folders over multiple workspaces  but this really requires to use the same plugins on all workspaces   You may want to consider using more project specific settings than workspace preferences in the future  So for instance all the Java compiler settings can either be set on the workspace level or on the project level  If set on the project level  you can put them under version control and are independent of the workspace

User · Answer

The only way I know to deal with this is to create a new workspace    import projects from the polluted workspace  reconstructing all my   settings  a major pain  and then delete the old workspace  Is there an   easier way to deal with this    For synchronizing or restoring all our settings we use Workspace Mechanic  Once all the settings are recorded its one click and all settings are restored    You can also setup a server which provides those settings for all users

User · Answer

In my case eclipse is not showing parent class function on  this  so I perform below mention points and it starts works -  I go to my  var www  folder and check for  metadata folder  Here check the  log file and it shows  Resource is out of sync with the file system  1  Go to Eclipse --  Project --  Clean  2  Windows -- preferences --  General --  Workspace --  And set it to  Refresh Automatically   After that boom - things gets start working     If you want to load variables from other files too then ado this  -  Eclipse-- Windows-- Preferences-- Php-- Editor-- Content Assist --  and check  show variable from other files   Then it will show element   variables and other functions also

User · Answer

One of the things that you might want to try out is starting eclipse with the -clean option  If you have chosen to have eclipse use the same workspace every time then there is nothing else you need to do after that  With that option in place the workspace should be cleaned out    However  if you don t have a default workspace chosen  when opening up eclipse you will be prompted to choose the workspace  At this point  choose the workspace you want cleaned up   See  How to run eclipse in clean mode  and  Keeping Eclipse running clean  for more details

User · Answer

In some cases  I could prevent Eclipse from crashing during startup by deleting a  snap file in your workspace meta-data   metadata  plugins org eclipse core resources  snap    See also https   bugs eclipse org bugs show bug cgi id 149121  the bug has been closed  but happened to me recently

[eclipse] Clean out Eclipse workspace metadata

Examples related to eclipse

Examples related to metadata

Examples related to configuration-files

Examples related to workspace

Examples related to eclipse-metadata