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.
xml (like new dependencies or plugins) and want Eclipse to be aware of them. mvn clean install. The first command deletes target directory and then builds all you code and installs artifacts into local repository.
If you've "installed" Eclipse but are having trouble getting it to run, the most likely cause is that you have not correctly specified the JVM for it to run under. You may need to edit the eclipse. ini file. Another common mistake on Microsoft Windows is a mismatch between the "bittedness" of Eclipse and the JVM/JDK.
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:
eclipse.ini
file located in your Eclipse install directory and insert -clean
as the first line. -clean
as the first argument. -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 eclipse-clean.sh
). (From: http://www.eclipsezone.com/eclipse/forums/t61566.html)
Other eclipse command line options: http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html
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.
You can start Eclipse in clean mode from the command line:
eclipse -clean
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.
it will take much time then normal start and it will fresh up all resources.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With