| Summary: | [external tools] project with just a program builder doesn't show up during clean | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Satyam Kandula <satyam.kandula> |
| Component: | Ant | Assignee: | Platform-Ant-Inbox <platform-ant-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Michael_Rennie |
| Version: | 4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Satyam Kandula
This is a bit confusing, but expected. We could probably do better to make sure that it shows up. More specifically, the reason is that when the build trigger is being asked for build modes it supports, the external tools framework reads the <stringAttribute key="org.eclipse.ui.externaltools.ATTR_RUN_BUILD_KINDS" value="full,clean"/> launch config property and reports back to the build framework. In the case of 'After a Clean' only the value of the aformentioned preference is "full", so the build framework ends up thinking the builder does not apply to a clean build, hence it does not show the project in the listing (also because there are no other registered builders that do support a clean build kind). See org.eclipse.core.externaltools.internal.model.BuilderCoreUtils for more information on how we configure build triggers. Thanks for the explanation. Actually I thought 'After a "Clean"' meant, truly after a clean, but I understand that it is supposed to be called before a build and after a clean. However, as 'After a "Clean"' builder can be triggered only on Clean, the project should be listed. As I understand this should be a build framework bug rather than Ant/External tools bug, right? 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. |