| Summary: | "Build Automatically" does not trust a preceding rebuild having occurred. | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Blessed Geek <blessedgeek> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | amj87.iitr |
| Version: | 3.8 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Blessed Geek
Are you sure you checked the "Start a build immediately" checkbox in the "Clean.." dialog? And within that you had the "build the workspace" option selected? If you did that, and then enabled build automatically, the build job trigger but ends up being a no-op. If you did not do that, the build job will ofcourse build the whole workspace since "Clean..." did not. Can you report back if you used the "Start a build immediately" option? I couldn't reproduce this with 3.7.1 or 3.8 (In reply to comment #1) > Are you sure you checked the "Start a build immediately" checkbox in the > "Clean.." dialog? And within that you had the "build the workspace" option > selected? Yes, because if I did not, it would not take an initial 15 minutes building the workspace. That is, the building workspace status appears twice. Is it because my projects have an ant build.xml file in each of them? Does "rebuilding workspace" trigger those ant build files? If so, and if any of the ant builds aborts, does it mean that eclipse would resolve the build again without the ant files when "build automatically" is set on? 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. -- The automated Eclipse Genie. |