Community
Participate
Working Groups
3.3 M 3 Steps to reproduce: 1. Use a workspace in which you have a few versioned Java projects (I used plugin projects) 2. Switch to the Java perspective 3. From the package explorer's view menu select Top Level Elements->Working Sets 4. If there are no other working sets defined, the projects will show up in the Other Projects working set 5. Select a working set with at least two projects in it 6. Close one of the versioned projects, making sure you have at least one other open 7. Select the working set, right click and try Team->Synchronize Observed behaviour: Sometimes the Team->Synchronize menu is disabled altogether, some other times it is enabled but when running the action a pop-up dialog with the message "The chosen operation is not enabled" is displayed. Expected behaviour: Allow the synchronization of all the projects which are open, and simply ignore the closed ones. More info: The current behaviour seems to be similar to what happens when projects are top level elements. In that case if you select opened and closed projects and try to synchronize, the Team->Synchronize menu is not even there. At least that's a better hint that you cannot synchronize. Ever since I noticed them, I am using Java working sets as top level because I like the ability to open/close/synchronize a set of projects at once. Some times though I may have a few projects which are not only closed but also filtered from view. It's frustrating to have to select all the opened projects in my working set and synchronize at that level.
+ 1 to enable synchronize even if some projects are not shared. Maybe you can show a warning dialog after, to say which projects have been skipped.
I'll try to have a look sometime during 3.3.
Sound similar to bug 139775.
This is probably a duplicate of bug 139775 but we'll keep them separate to ensure that both cases are covered.
Patch from bug 139775 has been released to HEAD which enables Synchronize on working sets that have unshared or closed projects.
Verified with 3.3 RC1
Closing since 3.3 is out and has the fix I requested.