Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 134498 - Allow workspace specific extension sites
Summary: Allow workspace specific extension sites
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Update (deprecated - use Eclipse>Equinox>p2) (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Update-Inbox CLA
QA Contact:
URL:
Whiteboard: obsolete
Keywords:
Depends on: 106169
Blocks:
  Show dependency tree
 
Reported: 2006-04-03 09:11 EDT by Gunnar Wagenknecht CLA
Modified: 2012-07-24 10:19 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2006-04-03 09:11:16 EDT 
It would be nice to have workspace specific extension sites. Currently whenever I install an extension via UM it is added globally. However, I don't need every feature in every workspace.

For example, in one workspace I need WTP but in another I'm developing Eclipse plug-ins where I don't want to have the WTP features available. Or in one workspace I'm working with Borland StarTeam or in another with EclipseNSIS but I don't want all these plug-ins available everywhere but only in this specific workspace.

Currently I have to create and maintain different installations of Eclipse. It helps me a lot that I can use ".link" files but it would be really great if I could configure workspace specific extension sites.
Comment 1 Dejan Glozic CLA 2006-04-03 10:41:22 EDT 
Gunnar, workbench UI has a notion of 'capabilities' that can be used here. Essentially what you want is to have workspace-specific UI filtering so that different capabilities are filtered out depending on the workspace.
Comment 2 Gunnar Wagenknecht CLA 2006-04-03 11:00:19 EDT 
No, I don't want to use capabilities for this. I want some features/extensions not loaded at all simply because I don't trust some extensions. They load themself on startup. They hook themself into projects/builders or other events. They consume memory and/or performance. There are many reasons. ;)
Comment 3 Dejan Glozic CLA 2006-04-03 11:44:09 EDT 
There are all valid reasons not to do it :-). Also a good example why lazy loading is so important in Eclipse. A plug-in should not be active just by the virtue of being in the configuration.
Comment 4 Dejan Glozic CLA 2006-04-03 11:44:30 EDT 
Change 'There' to 'These' above.
Comment 5 Jeff McAffer CLA 2006-10-14 07:18:47 EDT 
Interesting approach.  There would be some potential conflicts with the framework caching etc since currently the framework caches the set of things to run in the configuraiton area.  What we are saying here is that really the configuration is related to the data that is being managed.  In the context of enabling user/role based provisioning we have talked about spliting the state and resolver information (the cache).  see bug 160958
Comment 6 John Arthorne CLA 2012-07-24 10:19:56 EDT 
The Eclipse Update component is no longer under development, and no longer exists in the Eclipse Platform 4.x stream. If this problem still occurs in Eclipse Platform 4.2 or later, please enter a new bug report against Equinox p2.