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

Bug 341320

Summary:	Working sets don't work properly in 3.7M6
Product:	[Eclipse Project] JDT	Reporter:	Nicolas Bros <nicolas.bros>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	markus.kell.r, prakash
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Nicolas Bros

2011-03-30 04:23:41 EDT

I'm using Eclipse 3.7M6 as my main development environment, and I am categorizing the many (java) projects in my workspace into working sets. I set "top level elements" to "working sets" in the Package Explorer.

With this configuration: 
- moving a project (drag&drop) from a working set to another often doesn't work
- moving several projects from a working set to another sometimes moves only a subset of the selected projects
- deleting one or several projects from a working set deletes the project(s), but leaves a "shadow" project in the working set : if I try to delete it, I get an error saying "no input element"

This is not blocking though, because the "Configure working sets" dialog seems to work properly to organize working sets.

Comment 1 Prakash Rangaraj

2011-03-30 04:51:22 EDT

Works fine for me.

Comment 2 Markus Keller

2011-04-01 09:25:14 EDT

Also works fine for me with Java working sets and Java/PDE projects. What kinds of working sets and projects are you moving around?

The problems with stale working set elements should have been fixed in 3.7M5 (bug 300368).

Can you try to find steps to reproduce the problem?

Comment 3 Nicolas Bros

2011-04-04 03:53:03 EDT

(In reply to comment #2)
> What kinds of working sets and projects are you moving around?
I have 12 Java working sets and a "resource" working set.
With many projects (a few hundred), mostly with the Java+PDE natures, but also some with Acceleo and ATL natures.

I'm also using subclipse on all these projects. I noticed it's sometimes blocking some operations like trying to move a file from a versioned project to a non-versioned one for example. Maybe it could be responsible for some issues with working sets too.

> The problems with stale working set elements should have been fixed in 3.7M5
I had the problems with 3.7M6, but I was using a workspace that I kept for many milestones. So it's possible that the workspace somehow got corrupted?

> Can you try to find steps to reproduce the problem?
I couldn't reproduce with I20110310-1119.
I'll comment on this bug if I stumble on these problems again.

Comment 4 Markus Keller

2011-04-04 13:33:46 EDT

Thanks for the info. Closing this bug for now. Please reopen if you have more information.

Note that instead of drag&drop, it's often easier to use the "Assign Working Sets..." dialog from the context menu.