Community
Participate
Working Groups
Feature Request: core and UI support for IWorkingSet of Java resources. We want the user to define the IWorkingSet using something like the current UI, but also be able to access the same working set in core code for running Eclipse in "headless" mode. Here is the e-mail thread from eclipse.tools: ----- Original Message ----- From: "John Arthorne" <John_Arthorne@oti.com_> Newsgroups: eclipse.tools Sent: Tuesday, January 14, 2003 8:44 AM Subject: Re: Core support for IWorkingSet > If you're only interested in java resources, take a look at > org.eclipse.jdt.core.IRegion. It defines a hierarchical subset of java > resources. This might be enough for your purposes, and it can be used > in a headless environment. > > Feel free to enter a feature request if this doesn't suit your needs. > However I can tell you now that there is little chance of getting this > addressed. We investigated core-level working set support for 2.1, but > decided we couldn't come up with a common definition of working sets > that was satisfactory for all users. In short, if it's generic enough > to go into core, then it's no longer useful enough for clients in the UI > and JDT. Some users wanted static sets like IWorkingSet, others wanted > rule-based sets like JDT, some needed change notification, some wanted > serialization and some didn't, etc... > - > > > Yaniv Inbar wrote: > > Feature request: core platform support in Eclipse 2.1 for working sets, or > > the ability to access the workbench's working set in core code. > > > > We are developing a plugin for Eclipse 2.1 that tests a working set of java > > resources. This allows the user to have granular control over which > > resources they require to be tested, rather than testing whole projects. > > > > Unfortunately, working sets are only available in UI code, and cannot be > > accessed in a core plugin that can be used in a command-line program, i.e. > > in "headless" mode. Hence, we can only support listing of projects in the > > command-line, rather than simply listing a working set name. > > > > Is there a work-around for this issue? What are the chances of these > > feature request being fixed for Eclipse 2.1 if I file a PR on it? > > > > Thanks, > > Yaniv Inbar > > Parasoft Corp > > > > >
Marking old enhancement requests that we don't intend to fix in the near future as RESOLVED LATER. This does not mean we will never do them, but it means we have no specific plans to address them.
[LATER->WONTFIX] The "LATER" bugzilla resolution is being removed so reopening to mark as WONTFIX.
