Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 351741

Summary: Working sets management API should not be in UI bundles
Product: [Eclipse Project] Platform Reporter: Konstantin Komissarchik <konstantin>
Component: IDEAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: daniel_megert, francisu, pwebster, remy.suen
Version: 3.7   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Konstantin Komissarchik CLA 2011-07-11 14:17:47 EDT 
The API for dealing with working sets is located in UI bundles...

org.eclipse.ui.IWorkingSetManager

This makes it impossible to implement a clean MVC separation for something equivalent to the basic project creation wizard's first page. The model and operation for project creation cannot be in non-UI plugins while supporting working sets. 

In my opinion, this is a pretty serious bug, but given how long this API has stood as is, I doubt that it would be accepted as bug. Filing as enhancement request instead.
Comment 1 Remy Suen CLA 2011-07-11 18:12:56 EDT 
It's unlikely we'd do anything about this in 3.x but it's certainly something we could consider in 4.x.

Konstantin, could you list the APIs that you're looking for here? I imagine it's more than just this one interface...?
Comment 2 Konstantin Komissarchik CLA 2011-07-11 18:27:21 EDT 
> Konstantin, could you list the APIs that you're looking for here? I imagine
> it's more than just this one interface...?

I don't have an exhaustive list because I basically had abandon integrating with working sets when I ran into this problem. The basic requirement is for listing, creating, updating and deleting working sets without depending on a UI plugin.
Comment 3 Dani Megert CLA 2011-07-12 03:03:32 EDT 
If we decide to do this separation, then bug 27519 should be reopened. So far the answer was always WONTFIX, but as Remy said, it might be different in 4.x.

*** This bug has been marked as a duplicate of bug 27519 ***