Summary: | [CommonNavigator] [WorkingSets] Build Working Set from Project Explorer View | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Axel Mueller <axel.carl.mueller> |
Component: | UI | Assignee: | Francis Upton IV <francisu> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | aleherb+eclipse, martinae, mdelder, Mike_Wilson |
Version: | 3.3 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: |
Description
Axel Mueller
2007-06-22 10:29:35 EDT
Passing to JDT for issues one and three. We bug 58085 to cover number two already. You should also pass this bug to CDT. Project explorer is platform.ui The Package Explorer adds the default menus through its PackageExplorerActionGroup. In this case, the "Build Project" menu action comes from CDT, and should therefore by contributed by the CDT to the org.eclipse.ui.IWorkingSet element type displayed in the tree when "Working Sets" are selected as the root elements. Moving to Anton for feedback. The Package Explorer is from JDT. CDT does not add the "Build Project" menu item to the Project Explorer context menu. It comes from the ResourceMgmtActionProvider. CDT only adds the "Build Clean" menu item. Anyway, I don't see a good reason why CDT should add the "Build Working Set" item. Platform concepts, like working sets, should be handled by the Platform. Hi Anton -- I missed that. I was under the impression the Build Project action from Platform was removed; but it's because I'm so used to working with auto-build on. I think it's reasonable for the Working Set Extension (contributed by Platform/UI) to contribute these menu items to Working Sets. Martin/Anton -- thoughts on whether this is critical or important for 3.3.1? Looks like a new feature -> 3.4 Okay -- will shoot for 3.4. Assuming the shot missed. Clearing the target milestone. 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. |