Bug 29394

Summary:	suboptimal handling closing/opening projects in autobuild
Product:	[Eclipse Project] JDT	Reporter:	Adam Kiezun <akiezun>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.1
Target Milestone:	2.1 M5
Hardware:	PC
OS:	Linux-GTK
Whiteboard:

Description Adam Kiezun

2003-01-13 11:27:02 EST

20030107
with autobuild off the sequence
- close a binary project (that your sources refer to)
- reopen
- build all
takes 10 seconds because build results (correctly) in a no-op

with autobuild off, after reopening the project you still get errors in the task
list
build all does not help
you have to make a no-op change in a file and save it - this removes the errors
but the whole thing takes 10x as much time

Comment 1 Kent Johnson

2003-01-13 14:53:36 EST

Please provide a more concrete example.

Also note that a closed project must be rebuilt in full since some information 
is discarded when its closed, thus making it impossible to handle the 
close/reopen case optimally.

Comment 2 Philipe Mulet

2003-01-14 04:55:56 EST

Moreover, when a project is closed, no indication is provided when it reopens 
in case it did change in the meantime on the file system. This is why we cannot 
trust a closed project to not have changed since last time we saw it.

Comment 3 Adam Kiezun

2003-01-14 05:27:29 EST

strange, i cannot reproduce anymore (it's fast now in the autobuild-on case)
the concrete example was 'close org.eclipse.core.update' (binary) in self 
hosting workspace (with all binary except for jdt.ui, jdt.ui.test, 
jdt.ui.tests.refactoring in source)

if nothing can be done (and i cannot reproduce), then ok for me to close

Comment 4 Philipe Mulet

2003-01-14 07:18:09 EST

Closing