Community
Participate
Working Groups
Build 20020501 1) Filter the navigator and packages view on some working set 2) Create a new project The new project doesn't appear in navigator or packages view. This makes sense once you remember that your view is showing a working set, but this is never what you want. When you create a new project, chances are you want to work on it. Over the past week of coop training I've seen that new users are caught by this every time. One possible solution: newly created projects could be automatically added to any working set that is currently being used in any view. This could also be a preference on each working set. The edit working set dialog could have a checkbox at the bottom to "automatically add new projects".
I don't think working sets should automatically add new projects to themselves. The working set itself does not know whether it is selected in any views, or even whether it's used for filtering a view. It may only be used as a search scope. Another option would be for the view to warn the user that the new project will not be visible, and perhaps offer to add it to the working set.
I like the working set dialog option suggested by John for its simplicity. However, you may not want to add new projects that are created anywhere, i.e., in any view. Consider post v2.
*** Bug 16303 has been marked as a duplicate of this bug. ***
Should consider comments in bug 16303 too when we address this.
Reopen for investigation
*** Bug 11477 has been marked as a duplicate of this bug. ***
Not for 2.1, defer.
You would want to include any resource and not just projects in any solution. See also bug 35486.
Reassigning to Nick since he is taking ownership of this component.
*** Bug 45098 has been marked as a duplicate of this bug. ***
Try renaming an existing project which is displayed in your current working set. It will disappear because the working set is not aware of the change. Maybe these are related: bug 15938 bug 82549
*** Bug 87905 has been marked as a duplicate of this bug. ***
*** Bug 138354 has been marked as a duplicate of this bug. ***
*** Bug 83889 has been marked as a duplicate of this bug. ***
*** Bug 82549 has been marked as a duplicate of this bug. ***
Maybe you could add a combobox in the wizard, where one could define a working set assignment for the new projects (or a new step in the wizard). By default this working set is empty if the wizard is selected via a menu. However, if you right click on a working set in the package explorer and select "Import..." then this working set should be used as default (at least this is what the user expects).
*** Bug 84179 has been marked as a duplicate of this bug. ***
*** Bug 75339 has been marked as a duplicate of this bug. ***
*** Bug 139265 has been marked as a duplicate of this bug. ***
*** Bug 164034 has been marked as a duplicate of this bug. ***
*** Bug 167814 has been marked as a duplicate of this bug. ***
Current solution (3.3)of Working Sets is not clear. Creation of a new project leads to confusion, because new project simply disappears. I would like to see a new page/fields in the wizards to select working sets the project should be assigned to. Maybe this requires some kind of references between projects and working sets (not only filtering)?
The explanation in comment #22 is exactly what I had in mind, and the very problem I run into everytime I create a new project.
Please note, that this problem does not exists when a project is checked out (check out as) from repository - there is a checkbox that allows to assign project to the working set.
When importing existing projects, it would be nice to have the ability to assign them to an existing working set. We check out several separated applications from source repository and import them. Each application is imported by invoking the Import Wizard. Then, we need to manually assign the projects of each application to their working sets. This is annoying and it could be simplified by adding a chooser for the target working set.
Comment #25 describes our use case exactly. To add another point, less experienced developers think that the project disappeared because they don't see it show up in the navigator when a working set was in use during the time of the import.
Two related problems that will be lost as duplicates if reported separately. When working sets are the Package Explorer Top Level Elements, there is no New right button menu for a Working Set. When working sets are the Package Explorer Top Level Elements, invoking right button New on a project within a working set creates the new project in Other projects rather than in the same working set as the project from which New was invoked.
*** Bug 177462 has been marked as a duplicate of this bug. ***
*** Bug 157444 has been marked as a duplicate of this bug. ***
Bug 157444 got fixed as a polish item for 3.3 M7: The new Java project wizard contains new input fields to specify the working set(s) the new project should go in. The fields are initialized by the selection and by the active filters in the package explorer. For 3.4 we would suggest to move this UI down to platform, so that all new project and import wizards can add this capability. Bug 97200 is also fixed: It is about the missing 'New' menu on the working set element in the package explorer.
Sorry, bug 150009 got fixed, which is a subset of bug 157444 (New Java project wizard, only).
*** Bug 186837 has been marked as a duplicate of this bug. ***
*** Bug 84800 has been marked as a duplicate of this bug. ***
*** Bug 195487 has been marked as a duplicate of this bug. ***
I filed bug 199904 for the API request to platform UI to take over the working set selection UI from the new Java project wizard so it can be used by all other project wizards.
The solution for new resources generated by "New" wizards is in place for all SDK wizards but the import case still needs to be covered.
(In reply to comment #36) > The solution for new resources generated by "New" wizards is in place for all > SDK wizards but the import case still needs to be covered. The Import Wizard is also now has the working set in it. Probably we should close this as works-for-me?
Something internally raised, with so much external agreement, numerous votes and many duplicates cannot be WORKSFORME. WORKSFORME is for problems that cannot be sensibly reproduced. If the various reported use cases are resolved it is FIXED otherwise it is surely still OPEN.
This was greatly improved by the fix for bug 199904 that added working set selection to the new project wizard. However, I think what most people are looking for is that new projects are automatically added to the active global window working set, if there is one. This isn't done yet.
The problem still exist in Build ID: 20110218-0911. The partial solution to add working set selection to the new project wizard is not sufficient as it is not generally available for all types of new project wizards. Furthermore, at least when stepped into a working set (via "Go Into"), the expected behaviour is that adding a new project to the workspace adds it to the (only) currently visible working set.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant please remove the stalebug whiteboard tag.
