Community
Participate
Working Groups
Thing I'm missing now is profile for configuration and active plugins. This is because I'm using eclipse to work with Java,Python,Ruby projects. When I'm in Java project there is absolutely no need for me to use Ruby plugins and so on. What I suggest is to create configuration/plugins profiles mechanism. With this I could start Eclipse with "Ruby" profile and have only workspace settings with plugins necessary for Ruby development. When I start platform with "Java" profile then there will be only set of plugins for Java development. Even in Java world only I can highlight different profiles: "Eclipse PDE", "J2EE" etc. It is matter of consideration if there should be way to associate profile with workspace. Profiles have to be defined and controlled by users. I'm not expecting to see predefined profiles shipped with platform.
We totally agree. This is (for the most part) already possible. Create your own configuration and start eclipse with it. Simple version, copy the Eclipse configuration dir somewhere else (e.g., c:\foo) and then start Eclipse using eclipse -configuration c:\foo. Set that configuration up however you like. Now the caveat is that defining these other configrations is not particularly easy today. That is something we intend to work on.
Is there any way I can help implementing?
Sorry for the delay here. For the most part this kind of function will come under the banner of the new provisioning work in 3.3 and beyond. The plan is to create a more comprehensive notion of "configuration" that has API associated with it as well as a manager/manipulator that would allow you to duplicate etc. Then it is a reasonbly short step to expose this function in a UI somewhere. Right now the low level work to enable this capability is just ramping up. Your offer to help is appreciated. I think once there is a clearer plan around the low level mechanisms it would be useful to have someone write a UI and test out hte functionality.
*** Bug 222476 has been marked as a duplicate of this bug. ***
e4 would be a great venue to explore this.
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.
It's not realistic to think this could ever be supported. :-(
