My eclipse runs horribly slow because I have thousands of plugins installed on it. I spoke with another friend who uses eclipse but he has none. I feel like none of these are necessary and I didn't even install so many. I have thousands of plugins and I tried reinstaling eclipse but I need to find a way to remove every single eclipse plugin.
Attempting to delete a plugin manually takes up to 5 minutes per plugin, so it could take me months or years before actually deleting all of these by hand.
Is there a feature in eclipse to delete all the plugins? Also I'm using WINDOWS XP
First, you need to understand that virtually everything in Eclipse is a plugin. Eclipse has a very small core runtime (Equinox) that loads all features from plugins. You can't just "delete every plugin" as doing so would leave you with nothing.
Also, just because a plugin is installed does not mean that it is always loaded or taking up resources. Eclipse uses a "lazy loading" architecture that will only load a plugin when some feature that it provides is actually invoked. Some plugins are probably written poorly in such a way that they are loaded too aggressively, but that would be the rare exception. So, in general, having lots of plugins is not a problem for performance.
If you do have a plugin that you want to remove, you can not just delete it from the plugins folder - as you've seen that will screw up your Eclipse installation. Don't do that.
One way to manage the features that you have installed, including installing ones that are able to be uninstalled, is to open the About dialog, then click the Installation Details button. There you'll be presented with a list of features that have been installed; you can select a feature and if it's possible to uninstall it the Uninstall... button will be enabled.
Often it's one bad third-party plugin/feature (not something from eclipse.org) that causes an Eclipse installation to have problems; try to find what it might be by process of elimination (uninstall all third-party plugins that you might have installed since your Eclipse was fresh).
Finally, as a last resort, it is trivial to remove Eclipse completely (just delete it from your file system) and re-install it fresh.
Having said all that, performance problems are usually due to an underpowered machine. What kind of processort do you have? How much RAM does your system have available after Windows boots up? Have you specified memory settings in eclipse.ini?
Related
I accidentally installed CodeMix malware when installing Anguar IDE plugin to my Eclipse4.6. Now everytime I open a JS file it shows CodeMix registration window and I am unable to open JS files if I don't provide my email account. I tried 3 times of unstalling CodeMix and then restarting Eclipse, but failed 3 times. Every time Eclipse says successfully uninstalled. However The virus/malware CodeMix is still there asking for my email account. It is a Windows10.
Question 1: How can I completely remove CodeMix?
Question 2: Is it a crime to develop something like CodeMix in US?
The best way to uninstall software installed from the Eclipse Marketplace is by using the Marketplace client itself. Simply go to Help > Eclipse Marketplace... entry, and then the Installed tab where you can click Uninstall.
Uninstalling software in Eclipse can be difficult if you try to do it from the Help > Installation Details approach as you either need to roll back all changes you've made by using a Revert to a previous point of the installation or find all plugins that you installed from the marketplace. If you miss some plugins when doing the manual approach, Eclipse won't fully remove it.
In this case, CodeMix is not actually "reinstalling" itself as your question reads like. It was just never removed by Eclipse itself.
The installation of mistakenly installed plug-ins can be undone as follows:
In Help > About Eclipse IDE hit the Installation Details button
In the Installation Details dialog, in the tab Installation History select the installation point before the mistaken installation and hit the Revert button
Please note that this does not delete files created by the plug-in itself. As far as I know, this plug-in creates a subdirectory in the user's home directory occupying a lot of disk space.
To the second question: As far as I know, not the development but the distribution can be illegal in the US, for example when spying without the user's consent or when licenses (including open source licenses) are violated.
There are about 6~7 CodeMix plugins including Angular, CodeMix Essentials and 3 more. I had to search by 'mix' and then remove everything in the search results. It is gone now.
As a work around I just went and removed everything it was trying to be the preferred editor for (CodeMix/Editors/Preferred Editors). It seems to have made it less of a problem.
I don't know if this applies to you, but in my installation Groovy Development Tools was interfering with adding and removing plugins. After removing that, I have been able to add and remove other things without difficulty.
I am using Eclipse 2020-12.
I installed CodeMix when I was looking for an editor for Go files. They definitely have an aggressive model when it comes to trying to monetize Eclipse plugins. I think it is a shame that they went so overboard on the marketing, because the product itself shows a lot of work, and I would have been willing to pay for something less intrusive.
That said, they now have a pretty good uninstaller built into the product. Just go to (in the Eclipse menu) Help > CodeMix > Uninstall CodeMix. This seems to have cleared it all out for me.
I do C++ embedded development for the NetBurner platform. They have plug-ins that customize Eclipse and in addition to a build tool-chain they add a Launch Group under the Run Configuration area. Everything was working fine under Indigo (32 bit) when I decided to install Subclipse (big mistake). As soon as the install finished I could no longer run my existing configurations successfully. When I went into the Run Configurations area I noticed the Launch Group I used to use was missing. Here is what it looked like earlier yesterday:
Here's what it looks like today:
Things I've tried
First I uninstalled the Subclipse plugins using the
Help->About->Installation Details and then selecting them one at a
time, Uninstalling and restarting after each uninstall. No change.
Then I unpacked the original Eclipse Indigo/CDT 32 bit download to a
fresh folder. Copied over the NetBurner plugins from the zip I got
from the manufacturer. No change.
Launched with different Workspaces, no change.
Launched a Galileo version, it uses older plug-ins, and it still
works.
Copied older plug-ins into Indigo, the older NetBurner launcher
shows up (but it doesn't really work with Indigo)
Removed the older plug-ins put in the newer ones, old NetBurner
launcher went away new launcher does not show up.
Tried removing the
{Workspace}.metadata.plugins\org.eclipse.debug.core.launches - no
change.
Interestingly even though launches has many .launch files that should show up under Run Configuration, nothing shows up.
One other strange (possibly relevant) thing is that icon for the NetBurner Perspective went away, now it just has <NetBurner> as the text and a generic perspective icon.
I can still cross-compile and build for the NetBurner (i.e. the build toolchain still works), it's just the ability to use run configurations that seems to be missing.
I'm out of ideas, does anyone know of some global setting that sits outside the workspace and outside the Indigo installation folder that could be causing this?
I'm running on Win 7 64 bit ultimate, I run the 32 bit version of Indigo because the 64 bit doesn't appear to work with the NetBurner plug-ins. I've also disabled the two Mylyn tasks under General->Startup and Shutdown (they seemed to cause many Permgen memory crashes). This is the same setup I had working flawlessly yesterday.
Update
I also noticed that only 3 of the 4plug-ins are showing up in the Installation Details plug-in pane. The nbeclipse.core_2.6.0.jar is in the eclipse plugin directory but not showing as loaded. So I guess I know now the problem is the plug-in isn't loading but I don't know why or how to get it to load, or what subclipse could have changed that would cause this.
I suspect that the Subclipse installation may have caused an update to some other plugin(s) that it depended on (keep in mind the transitive nature plugin dependency resolution; if you're installing plugin A and it requires a certain version of Plugin B that you don't have, Plugin B will be installed or updated to that version). In doing so, maybe the NetBurner plugin can no longer load because its declared dependencies are no longer met (ie, it depended on an earlier version and does not tolerate a later version).
You can use the OSGi Console to help determine why a plugin is not loading. Here are a couple of references that should help:
http://grep.elasticpath.com/community/techblog/blog/2010/05/27/eclipse-plugins-and-the-osgi-console
http://www.vogella.com/articles/OSGi/article.html#osgiconsole
By the way, you can not just copy plugins into an Eclipse installation and expect them to work. For several versions now, Eclipse has not supported that ability. You must use Help > Install New Software or File > Import > Install > From Existing Installation to install plugins. Ask the vendor if they have an update site to install from; like I said above, simply dropping things into Eclipse's plugins folder is not supported any more, it won't work. Other than the vendor providing an update site, the only other option is to use the dropins folder, as described here.
Bootstrapping Eclipse on new machines is such a time consuming process, you wind up asking yourself whether you really need each plugin. But there all handy, and help develop consistent habits.
Eclipse bootstrapping problems include:
Explaining / documenting what needs to happen
The actual time pasting in the right URLs and downloading
Version compatibility and dependencies
Eclipse likes to restart after each one
The changeover to the Eclipse Marketplace means that some plugins and instructions you find on the web tend to be inconsistent, depending on when they were written.
The Licenses... over and over and over... yes, yes, yes... I understand that the person installing needs to be aware of it, and have a chance to review them, but there's got to be a better way.
It'd be nice to have "patch file" (either binary or meta) that spells out what I want to add on top of stock Eclipse installation. I'd really like to find (or create) a 1 or 2 step process that sets up Eclipse, plus a favorite batch of plugins:
subclipse
m2eclipse
jetty support like runjettyrun
android sdk and plugin (or at least just the plugin)
aspectj
Web Objects / WOLiops
python, other langs
JVM Monitor, maybe EclEmma
probably a git plugin pretty soon.
Does command line maven help with any of this? It seems like its repository management would fit at least part of the functionality.
On a machine with an Eclipse installation matching your needs use File -> Export -> Install -> Installed software items to file. Import the generated file using the same menu on all other machines.
As Scott says, a good approach is to simply package a fully prepared Eclipse installation once all the plugins you need are installed. The downside is that you have to update most plugins afterwards.
Another option is to use Yoxos. With it, you can create a profile and configure it with all the plugins you need (and apparently Yoxos can do more than that).
Finally, this page might interest you concerning the configuration side of things.
Solution 1 is too search for more advanced Eclipse distributions.
For example, STS (Spring Tool Suite) comes with
AspectJ
EGit
m2e
(and of course) Spring IDE
One small trick can be done with m2e-android - Android Configurator for M2E Maven Integration. If installing it on clean Eclipse, it will also automatically resolve to install :
m2e
Android Developer Tools (ADT)
How do you manage your Eclipse installation, i.e. the basic installation, plug-ins and workspace settings with regard to consistent updates (including major ones, 3.5 => 3.6) and usage on two or more computers (desktop + notebook).
My current setup is to basically managing the installation on several installations in parallel, i.e. manually add new plug-ins I installed on one to the other, and when I haven't used one in a long time to copy the whole directory from one location to the other.
For updates I usually run it about once a month to get the latest versions, major updates I do manually by downloading the basic distribution and re-installing all the plug-ins in the matching version for the new major Eclipse version.
However, this approach has some drawbacks:
time intensive
update inconsistencies (Update sites change location, update doesn't work because of some version inconsistency between plug-ins that requires a lot of manual fixing, etc) (this has gotten better with 3.5 but still bugs me)
no "global" update site, I manually have to manage several locations
I tried alternatives like Yoxos for configuration management but there plug-ins were missing and / or not that well tested together as I expected.
I took a look at Idea as an IDE, the one thing I really loved was the update management: centralized and 90% of the functionality I'd be using are provided as a core that is tested and updated as one.
Thus the question: How do you manage your Eclipse installations and deal with updates?
From my experience with other Eclipse users they have at least the same problem with updates, but I haven't heard of a solution yet.
I've heard good things from other developers about Google's Workspace Mechanic.
That's what they use inside Google to manage Eclipse environments across teams.
It was open sourced in May 2010, and you may find more information in the blog post.
Note that the Workspace Mechanic does not yet manage plug-in installations (see discussion thread): it remembers "plugin preferences", but installing the plug-in themselves is not yet supported.
I also met such inconvenience. I always need install similar development tools(such as Mylyn, SVN, CDT, Clearcase) in different eclipse instances on different hosts(Windows, Linux).
Update:
Eclipse has officially offered a feature to help migrating what you have installed since Eclipse Indigo.
And it also supports install existing plug-ins from another instance.
My strategy is as follows:
When a new Eclipse version comes out, I install it fresh and set up a fresh workspace. Then, I install all the minimal plugins I need manually, such as Subversion and M2Eclipse. Also, I export the preferences (e.g. code formatting) to an external file and reimport it in the new Eclipse installation.
I always import existing projects into the workspace. I can use my workspaces (or better, my SVN working copy) from multiple Eclipse versions if necessary.
I only occassionally install additional Eclipse plugins and try to move all other toolchain parts into the build environment (e.g. Hudson with several slaves, automated builds and release scripts, Sonar for code-quality reports etc.)
I try to minimize the complexity of the development setup on my local developer machine.
I only have one installations but I have multiple workspaces.
I synchronize the workspace setting by copying the content of <workspace_dir>/.metadata/.plugins/org.eclipse.core.runtime/.settings directory.
I also use the bookmarks to centralized to save the update-sites relevant for my work. This can act as a global update site. To import/export some bookmarks, go in Preferences -> Install/Update -> Available software sites. When a new Eclipse version comes out (once a year), I only have to install the plugins using the bookmarks.
Eclipse can contains a lot of different feature set via plugins.
Do you install all the plugins in one single eclipse? or do you install STS from spring, Flex eclipse from adobe, or even RCP development bundle from eclipse.org, every eclipse variant handle its task respectively?
Which way do you prefer and why? speedy response? avoid the hassle of updating/installing plugins?
Thanks
If you have enough power on your workstation (and the right eclipse.ini), you can:
install all the major plugins in one operation (choosing the most complete distro, like the J2EE one)
install any other external plugins in a shared directory (meaning those plugins will continue to be referenced by any new version of eclipse distro you may install in the future)
In eclipse I prefer to install them separately, because it seems to keep things running smoothly, no upgrading things as they come along, only as a whole thing, it makes for a lot of duplication though... With Netbeans (which I prefer) I generally install everything in one place and it too runs smoothly, even when I upgrade different plugins and add and remove other ones.
I separate groups of related plugins/features by defining separate install locations (You used to be able to do it through the IDE, can't find the right button at the moment, see here for some guidance on doing this manually). That way you can enable/disable groups if you need to.
The install locations can also be shared between different Eclipse installs (with care!), and if you completely trash or want to upgrade Eclipse, you can redefine the eternal locations on the new install, no downloads needed.