Bug 64056 - Repeated builds on startup
Summary: Repeated builds on startup
Status: RESOLVED DUPLICATE of bug 63756
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.0 RC1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-26 05:10 EDT by Andre Weinand CLA
Modified: 2004-05-26 07:40 EDT (History)
0 users

See Also:

Attachments
progress dialog (44.67 KB, image/jpeg)
2004-05-26 05:11 EDT, Andre Weinand CLA 		no flags Details
Console tracing output (432.08 KB, text/plain)
2004-05-26 05:13 EDT, Andre Weinand 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 Andre Weinand CLA 2004-05-26 05:10:19 EDT 
M9

With M9 I see the following annoying behavior on startup Eclipse with my development workspace:
- first, after startup everything looks OK, however, if I open the Package Explorer (a FastView),
   a build kicks in with the progress dialog (see attachment).
- after some time the dialog disappears and it appears that I could start working. However,
   clicking somewhere (or just waiting a few seconds) presents another progress dialog
   and the build continues.
- this goes on and on. Eventually (after 10 minutes) building stops with either thousands of
   errors (due to some build path problems) or everything is fine.

I have enabled jdt.core tracing and have attached the resulting trace (this trace corresponds to a 
workspace where the build process resulted in a single (but bogus) build path problem.
Comment 1 Andre Weinand CLA 2004-05-26 05:11:50 EDT 
Created attachment 11122 [details]
progress dialog
Comment 2 Andre Weinand CLA 2004-05-26 05:13:15 EDT 
Created attachment 11123 [details]
Console tracing output
Comment 3 Philipe Mulet CLA 2004-05-26 07:40:55 EDT 
Thanks for the traces.

*** This bug has been marked as a duplicate of 63756 ***