Community
Participate
Working Groups
Build Identifier: 20110218-0911 Over a period of time for which I've been using Eclipse (around 7 years) I've used it for various different tasks (and not only for Java development). During these years, I've faced a very basic problem which none of the Eclipse versions has solved. Currently, different Eclipse installations are necessary for different types of usage of Eclipse (e.g. one installation with all modelling related plugins, another for development plugins, and yet another for testing). If we include all the plugins together in the same installation, this causes Eclipse to become very heavy (in terms of resource utilization) and hence causes a lot of issues in terms of responsiveness and speed of execution of different commands/tasks. Can we try and add a concept of "plugin profiles" (or some better word!) where, during the start up, similar to selection of workspace, user can choose to start a particular "profile" containing the pre-defined set of plugins. User can then manage the plugin profiles as per their needs and only enable the profile which is required for the work they are starting Eclipse for. This can create a single local repository of plugins for Eclipse installation, and profiles can then choose (and hence activate) only the plugins that are required for the current session of Eclipse. This will also help manage the runtime size of Eclipse in spite of having all the plugins within same Eclipse installation. I'm not sure if this or similar functionality is currently possible using an existing feature. However, I have not come across any such feature yet. Reproducible: Always Steps to Reproduce: NA
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
