Description John Arthorne 2004-06-09 18:29:14 EDT

I20040609 1200

1) Switched to the Java perspective and then quickly did Ctrl+Shift+T. 
2) Got a "User operation is blocked dialog". 
3) Clicked the cancel button on the "User Operation" entry in the dialog.
4) The operation canceled as expected.

I am now in a state where all Java tooling is broken. F3 doesn't work, type
hierarchy doesn't work, etc. The Problems view shows no problems in the workspace.

5) Modify a file and hit save (autobuild is on).

Now I get the following problem marker on all projects:

The project was not built since its build path is incomplete. Cannot find the
class file for java.lang.Object. Fix the build path then try building this project.

I had to shutdown, restart, Clean the workspace, and do a full build to get back
into a good state. It seems that JDT isn't recovering from the cancelation of
the build path initialization.

Note: I was testing this scenario heavily in 3.0 RC1 and didn't find any
problems. It seems like there is a recent regression here. CCing Wassim as it
could possibly be caused by the PDE classpath container.