Accepted answer

what it does:

if set to "true", any cached data used by the osgi framework and eclipse runtime will be wiped clean. this will clean the caches used to store bundle dependency resolution and eclipse extension registry data. using this option will force eclipse to reinitialize these caches.

how to use it:

  • edit the eclipse.ini file located in your eclipse install directory and insert -clean as the first line.
  • or edit the shortcut you use to start eclipse and add -clean as the first argument.
  • or create a batch or shell script that calls the eclipse executable with the -clean argument. the advantage to this step is you can keep the script around and use it each time you want to clean out the workspace. you can name it something like eclipse-clean.bat (or


other eclipse command line options:


this will clean the caches used to store bundle dependency resolution and eclipse extension registry data. using this option will force eclipse to reinitialize these caches.

  1. open command prompt (cmd)
  2. go to eclipse application location (d:\eclipse)
  3. run command eclipse -clean


for windows users: you can do as rta said or through command line do this: navigate to the locaiton of the eclipse executable then run:

 eclipse.lnk -clean

first check the name of your executable using the command 'dir' on its path


two ways to run eclipse in clean mode.

1 ) in eclipse.ini file

  • open the eclipse.ini file located in the eclipse installation directory.
  • add -clean first line in the file.
  • save the file.
  • restart eclipse.

enter image description here

2 ) from command prompt (cmd/command)

  • go to folder where eclipse installed.
  • take the path of eclipse
  • c:..\eclipse\eclipse.exe -clean
  • press enter button

enter image description here


easier option is to use ./eclipse -clean


for mac os x yosemite i was able to use the open command.

usage: open [-e] [-t] [-f] [-w] [-r] [-n] [-g] [-h] [-b <bundle identifier>] [-a <application>] [filenames] [--args arguments]
help: open opens files from a shell.
      by default, opens each file using the default application for that file.  
      if the file is in the form of a url, the file will be opened as a url.
      -a                opens with the specified application.
      -b                opens with the specified application bundle identifier.
      -e                opens with textedit.
      -t                opens with default text editor.
      -f                reads input from standard input and opens with textedit.
      -f  --fresh       launches the app fresh, that is, without restoring windows. saved persistent state is lost, excluding untitled documents.
      -r, --reveal      selects in the finder instead of opening.
      -w, --wait-apps   blocks until the used applications are closed (even if they were already running).
          --args        all remaining arguments are passed in argv to the application's main() function instead of opened.
      -n, --new         open a new instance of the application even if one is already running.
      -j, --hide        launches the app hidden.
      -g, --background  does not bring the application to the foreground.
      -h, --header      searches header file locations for headers matching the given filenames, and opens them.

this worked for me:

open --args clean


  • click on short cut
  • right click -> properties
  • add -clean in target clause and then start.

it will take much time then normal start and it will fresh up all resources.


using the -clean option is the way to go, as mentioned by the other answers.

make sure that you remove it from your .ini or shortcut after you've fixed the problem. it causes eclipse to reevaluate all of the plugins everytime it starts and can dramatically increase startup time, depending on how many eclipse plugins you have installed.


you can start eclipse in clean mode from the command line:

eclipse -clean


for clean mode: start the platform like

eclipse -clean

that's all. the platform will clear some cached osgi bundle information, it helps or is recommended if you install new plugins manually or remove unused plugins.

it will not affect any workspace related data.

Related Query

More Query from same tag