Summary: | build workspace operation launched after each startup | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Eric Jodet <eric_jodet> | ||||
Component: | Core | Assignee: | Eric Jodet <eric_jodet> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | frederic_fusier | ||||
Version: | 3.2.1 | Keywords: | contributed, performance | ||||
Target Milestone: | 3.3 M5 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Eric Jodet
2007-02-01 04:43:31 EST
Created attachment 57987 [details]
Proposed fix
This patch prevents jdt.core to trigger a build when initializing containers.
Released for 3.3 M5 in HEAD stream. I can still see a "Building workspace job" on startup. So it seems that there is still a rebuild triggered on startup. Closing as VERIFIED. I added an .option file to get tracing of the build activity and I could not get an entry for the builder on startup. So even if the progress view shows a build job very quickly, there is no actual build on startup. Verified for 3.3M5 using I20070205-0009. Fix released in Startup_R32x branch. |