Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 82699

Summary:	Open Type on startup triggers long build
Product:	[Eclipse Project] JDT	Reporter:	John Arthorne <john.arthorne>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	dj.houghton
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description John Arthorne

2005-01-12 14:13:39 EST

Build: I20050112

I'm still trying to get to the bottom of this, but here is what happens:

- Self-hosting workspace with several plugin projects (I have org.eclipse.core.*)
- Java perspective, no editors open
- Shutdown Eclipse
- Restart
- Immediately after startup, Do Ctrl+Shift+T
- If you see no dialog, press Ctrl+Shift+T repeatedly
- when dialog opens, immediately close it
- press Ctrl+Shift+T again

After repeating similar steps, I can always get a build to run.  The build takes
about ten seconds, and I can see from builder tracing that it is indeed invoking
the JavaBuilder on several projects.  No build should be started since nothing
has been modified.

Comment 1 Dirk Baeumer

2005-01-12 14:48:52 EST

We are trying to get rid of the all types cache for 3.1 However, the all types
cache does a search which itself triggers class path initialization. As reported
in bug 73969 this (can) trigger builds due to problems in PDE class path
initializers (see bug 73969 for more details)

Moving to core for comments. I assume this is a dup of 73969

Comment 2 John Arthorne

2005-01-12 15:04:05 EST

After reading bug 73969 I'm pretty sure this is a duplicate.

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