Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363338 - "Build Automatically" does not trust a preceding rebuild having occurred.
Summary: "Build Automatically" does not trust a preceding rebuild having occurred.
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-09 10:56 EST by Blessed Geek CLA
Modified: 2019-12-13 06:01 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blessed Geek CLA 2011-11-09 10:56:38 EST
Build Identifier: M20110909-1335

Executing "Clean all projects and allow Rebuild" does not prevent another rebuild when "Build Automatically" is toggled back on.

I have ten workingsets, each of which has about 10 - 20 projects. So, I have to turn "Build Automatically" off to prevent thrashing while the projects are being imported.

Reproducible: Always

Steps to Reproduce:
1. Use tortoise svn to check projects out into working dir.
2. Start Eclipse on a virgin workspace and turn of "build automatically".
3. Import those hundreds of projects from the svn working dir without copying them into workspace.
4. Project -> Clean ... Choose Clean all projects and allow rebuild after clean.
5. Wait for 15 minutes for all the projects to complete cleaning and rebuild.
6. Turn "Build automatically" back on.
7. "Build automatically" does not seem to trust Clean-rebuild's having completed the rebuild, because now I have to wait another 15 minutes for a second rebuild to complete.
Comment 1 Ayushman Jain CLA 2011-11-09 12:49:33 EST
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
Comment 2 Blessed Geek CLA 2011-12-08 10:42:56 EST
(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?
Comment 3 Eclipse Genie CLA 2019-12-13 06:01:38 EST
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.