Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319623 - Reboot triggers a rebuild
Summary: Reboot triggers a rebuild
Status: CLOSED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2010-07-12 14:41 EDT by Gary Karasiuk CLA
Modified: 2012-03-19 05:21 EDT (History)
3 users (show)

See Also:

Attachments
build options turned on (15.85 KB, text/plain)
2010-07-12 14:43 EDT, Gary Karasiuk CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Karasiuk CLA 2010-07-12 14:41:44 EDT 
I'm not sure how to debug this, but I have a problem that a build is triggered when I reboot my system.

I'm using a adopting product. I have auto build turned on.

If I don't reboot my system, restarting my product, does not trigger any builds. But as soon as I reboot my system, the next time I start my product it will also trigger a build. 

I turned on build tracing (which I have attached), but I still can't tell what is triggering the build.
Comment 1 Gary Karasiuk CLA 2010-07-12 14:43:02 EDT 
Created attachment 174085 [details]
build options turned on
Comment 2 Olivier Thomann CLA 2010-07-12 14:50:21 EDT 
Are you properly closing Eclipse when you reboot ?
Comment 3 Gary Karasiuk CLA 2010-07-12 16:12:23 EDT 
(In reply to comment #2)
> Are you properly closing Eclipse when you reboot ?

Yes, I stop it before I reboot. (I wait for the process to terminate before I reboot).
Comment 4 Olivier Thomann CLA 2010-07-15 11:14:17 EDT 
We would need more details. I never got the case myself. Are you sure the build is doing something ?
Comment 5 Olivier Thomann CLA 2010-07-22 10:55:57 EDT 
Jay, it looks like the container initialization triggers a new build on every restart.
Gary, please provide a reproducable case for Jay so that he can investigate what is going on.
Steps to reproduce are required for further investigation.
Comment 6 Jay Arthanareeswaran CLA 2010-07-26 02:08:17 EDT 
The InitializeAfterLoadJob runs as it normally would on start-up. The rebuild seem to be decided by the call ElementTree#hasChanges() from Workspace#endOperation() line number 1180. I don't quite know what goes in there.

Moving to Platform for further investigation.
Comment 7 Szymon Brandys CLA 2010-07-26 07:52:12 EDT 
Gary, does it also happen on vanilla Eclipse SDK?
Comment 8 Gary Karasiuk CLA 2010-07-26 09:22:27 EDT 
(In reply to comment #7)
> Gary, does it also happen on vanilla Eclipse SDK?

I have not tried this on vanilla Eclipse. This application requires a number of adopter class path containers, so I don't think it would build in vanilla Eclipse.

What I'm looking for is some pointers, so that I could debug this and determine if this is a platform problem or a adopter problem.
Comment 9 Gary Karasiuk CLA 2012-03-16 16:18:51 EDT 
Can you please close this bug.
Comment 10 Szymon Brandys CLA 2012-03-19 05:21:57 EDT 
Closed as per the reporter request.