Bug 96331 - InitializeAfterLoad seems to trigger a build
Summary: InitializeAfterLoad seems to trigger a build
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 RC2   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-23 13:50 EDT by Dirk Baeumer CLA
Modified: 2005-06-08 17:48 EDT (History)
0 users

See Also:

Attachments
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 Dirk Baeumer CLA 2005-05-23 13:50:06 EDT 
Now that we call initializeAfterLoad I see the following behaviour when I start
Eclipse:

- initializeAfterLoad job is running
- right after that I see a build job running.

From time to time (I don't have a pattern yet or a reproducable case) the build
is a full build.
Comment 1 Olivier Thomann CLA 2005-05-27 14:55:58 EDT 
This might be a side-effect of bug 95931.
Comment 2 Philipe Mulet CLA 2005-06-08 10:28:42 EDT 
Dirk - is this still an issue ? Normally, when autobuild is on, a build should
kick in if some classpath is changing or some external JARs did change.
Otherwise it should not perform any build.
Comment 3 Dirk Baeumer CLA 2005-06-08 16:11:16 EDT 
Haven't seen it lately.
Comment 4 Philipe Mulet CLA 2005-06-08 17:48:31 EDT 
Closing then.