Bug 20689

Summary:	[resources] Opening a closed project misses some deltas
Product:	[Eclipse Project] Platform	Reporter:	Kent Johnson <kent_johnson>
Component:	Resources	Assignee:	Platform-Resources-Inbox <platform-resources-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	major
Priority:	P3	CC:	airvine, dj.houghton, gunnar, krzysztof.daniel
Version:	2.0	Keywords:	investigate
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Kent Johnson

2002-06-19 17:42:39 EDT

F3

1. Start with a new workspace with org.eclipse.ui & all of its prereq projects 
down to org.eclipse.swt + swt.win32 imported from source.

2. Close org.eclipse.swt and org.eclipse.swt.win32 together.

3. Reopen just org.eclipse.swt

Notice that it was never rebuilt even though it depends on swt.win32 which was 
closed after it was last built and this close operation should show up as a 
delta.

Comment 1 John Arthorne

2002-06-20 11:52:27 EDT

Given two projects, A and B, where B referencs a JAR in project A.  Steps to 
reproduce the problem:

1) Close B
2) Close A (or delete the JAR in A)
3) Open B

-> It should have a build error, because it depends on a JAR that is now 
missing, but it doesn't.

When B is closed, we only save the tree state for the subtree rooted about B.  
When B is reopened, we don't have enough information to calculate what has 
changed in project A.  Basically the delta for A appears to be empty, so we 
never call the builder on B.

We need to save the last built state for every project that B depends on (the 
only alternative would be to force a full build on project open).

Not planning to fix for 2.0.

Comment 2 DJ Houghton

2004-04-29 10:25:25 EDT

Deferring to post 3.0.

Comment 3 Lars Vogel

2019-09-24 13:57:54 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.