Bug 227262 - [WorkingSets] Select working set to clean.
Summary: [WorkingSets] Select working set to clean.
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2008-04-15 23:42 EDT by Yuejie Chen CLA
Modified: 2019-09-06 16:15 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuejie Chen CLA 2008-04-15 23:42:31 EDT
Currently, we can clean all workspace projects or selected projects to clean and rebuild. It will be more convenience if UI can select one or more working set to clean.

To not break current UI, I think group the project selection tree by working sets is the simplest solution. Maybe, we just need add a button to switch group by working set or not in the Clean dialog.
Comment 1 Kim Horne CLA 2008-04-17 09:33:31 EDT
I'm not sure I fully understand your request.  I understand that you want to clean a particular working set but I dont understand your suggested solution.  Do you want an action on the top level working sets shown in the package/project explorer?
Comment 2 Yuejie Chen CLA 2008-04-17 22:25:47 EDT
I want a toggle action in Clean dialog(Menu bar->Project->Clean...) that can group projects in working set or not.

Yes, we can set package explorer top level as working set, then select working set, and open the Clean dialog, the dialog will automatically select the projects in the selected working sets. But if the Clean dialog can group projects in working set, it will be more convenient to do projects manipulation when the workspace has dozens of projects.
Comment 3 Kim Horne CLA 2008-04-18 10:38:26 EDT
Okay, I understand now.  This seems like a reasonable request.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:15:28 EDT
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.