Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

FAQ How do I remove a plug-in?

Depending upon the particular version of Eclipse you are running with, the difficulty of uninstalling features or plugins from an Eclipse installation ranges from trivial to painful. In some cases, Eclipse doesn't support uninstalling certain 'optional' features after they have been installed.

Run Help > About Eclipse > Installation Details, select the software you no longer want and click Uninstall. (On Macintosh it is Eclipse > About Eclipse > Installation Details.)

In older versions, you might need to Run Help > Software Updates > Manage Configuration..., select the feature of interest, and disable it with the task shown in the right window.

'Uninstalling' a feature, using the steps above, disable the feature or plug-in. These steps are using the Update Manager under the covers.

When a feature is disabled, all its plug-ins will be disabled also. They are still available on disk, and they can be enabled at any time in the future.

There is no mechanism within Eclipse to permanently and physically uninstall a feature and its plug-ins. The process to physically and permanently remove an undesirable feature and its plug-ins is a manual process that should be done when Eclipse is not running. In order to do, you will have to manually remove the files there associated with the feature from the eclipse/features directory and its plug-ins from the eclipse/plugins directory. Be very cautious as to which files you delete, and always have a backup of your Eclipse directory. If you remove the wrong files from these directories, you may have quite some trouble restoring your Eclipse to a stable state. Therefore, unless your hard disk storage capacity is extraordinarily limited, it is recommended that you simply leave the physical files in place.

Note that when manually removing plugins as described above, it is likely that some metadata will still cached by Eclipse. This can lead to problems later on. Running Eclipse with the -clean option may help with that, as it causes Eclipse to clean the cached metadata. See the Running Eclipse help page for details about this option.

Comments from the peanut gallery

There are legitimate use cases for wanting to safely remove a particular plugin, such as rolling back to a previous version, repairing a corrupted plugin, or eliminating conflicting plugins?

Under Helios/3.6/STS it's impossible to remove plug-ins or disable features. You can disable a few plugins at startup via "Window > Preferences" from the menu under "General > Startup and Shutdown". Uncheck the items you don't want to run when you start Eclipse. This needs to be done for every workspace. To remove a plug-in you need to remove the JAR file from the "plugins" directory, located in your Eclipse installation directory.

Under Indigo/3.7 the "Help > About Eclipse > Installation Details > Installed Software tab > Uninstall..." option works. For some.

Under Helios I had none of the menu items mentioned above. I went to Help -> Install New Software... ; clicked the small blue hyperlink for What is "already installed"; and under the Installed Software tab, this gave me (contrary to the notes above) the option to uninstall things. I used it to uninstall PyDev, which was creating conflicts for me with Java development.

This is the type of error message gives rise to the typical use-case for uninstalling a plugin: Cannot complete the install because of a conflicting dependency.

 Software being installed: m2e - Maven Integration for Eclipse (
 Software currently installed: Project configurators for commonly used maven plugins (temporary) (
 Only one of the following can be installed at once: 
   Maven Integration for Eclipse (org.maven.ide.eclipse
   This version of m2eclipse cannot be installed on top of the already installed m2eclipse. Uninstall the previous version of m2eclipse and try the install again. (org.maven.ide.eclipse
 Cannot satisfy dependency:
   From: m2e - Maven Integration for Eclipse (
   To: bundle org.maven.ide.eclipse []
 Cannot satisfy dependency:
   From: Plexus Metadata Generation (org.maven.ide.eclipse.plexus.annotations
   To: bundle org.maven.ide.eclipse [0.10.0,0.13.0)
 Cannot satisfy dependency:
   From: Project configurators for commonly used maven plugins (temporary) (
   To: org.maven.ide.eclipse.plexus.annotations []

This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.

Back to the top