Description Mike Wilson 2001-10-10 23:00:27 EDT

When we load our org.eclipse.swt project it generates several thousand items
	in the task list because our .classpath file is not set. When I copy our ".classpath_motif"
	file to ".classpath", all items disappear from the task list, but the red x on the
	org.eclipse.swt _project_ in the Packages view does not disappear.

NOTES:

	McQ (02/06/2001 11:16:07 AM) -
		Could be an SWT problem, since it seems to go away on Windows.

	EG (6/3/2001 4:42:36 AM)
		Don't think it is an SWT problem, looks like an error tick update problem.
		This is the 2nd error tick update problem since 114. 

TM (23.07.2001 11:45:28)
	Have a scenario:

	1) create a project P
	2) create two source folders: F1 and F2
	3) create the same class foo.Foo under both source folders
	4) remove one source folder from the classpath.
	5) in the class remaining on the build path, introduce an error (call a non-existing method)
	6) remove F1 from the build path and put F2 on it. Do this in one step (only open the build paths
		page once)
	7) observe: there remains an error on the project, even though there should be none.
		Closing and reopening the packages view fixes the problem => refresh problem.

TM (23.07.2001 11:56:11)
	We're only looking at error deltas inside package fragement roots. Since the error is removed
	by removing the pkg fragment root, we never look at that change.
	Problem: since we're using resource deltas, we have no way to determine whether a change of 
	package fragment roots occurred.

TM (23.07.2001 16:16:52)
	Have fix.