Community
Participate
Working Groups
I have seen this reported elsewhere but on 3.0 betas mostly. Trying to iteratively debug my code I am tweaking my JUnit test cases and launching them again. Frequently, the launching window comes up indicating "The user operation is waiting for background work to complete" and indicating above that "The user operation is waiting for "Building workspace" to complete." The workaround is to change the workspace perferences to Prompt when waiting for the build to complete when launching. I have tried running Eclipse under JDK 1.5.0 and 1.4.2. I've alternated between JDK 1.3.1_09, 1.4.2_02, and 1.5.0 as my compiler but this problem remains.
This sounds like the expected behaviour. If it did not wait for the build to complete, you could be launching against out of date class files. There are a variety of preference settings under Run/Debug > Launching that allow you to change this if desired. Can you clarify what you believe the bug is here?
The problem is that it never clears, and I cannot stop that "build". I can go to lunch, come back and it is still not cleared. There is a comment on the message forums with a suggestion that something could be broken in the compiler notifying Eclipse that the build is done. I have done a Clean..., rebuilding the whole workspace and when I try to launch I still get this message. The other workaround is to close Eclipse and restart, which also clears the problem for the next run, though after my next change the problem returns.
Ok, that wasn't clear from the original description. Darin & Darin, have you heard of this happening? It could be related to some bugs we recently discovered with the IJobManager.join implementation, which I believe is used to wait for the build to complete. See bug 77039.
I have not heard of this happening. We do join an existing build if the user has asked to "wait for build before launching". See the code in DebugUIPlugin.launchInBackground(...).
Is there any other information I can offer to help diagnose this?
I'm suspecting the join is at fault. Stephen, once a fix for that is released you can help by verifying it if you like. I haven't reproduced the problem here.
Marking as a duplicate of the bug in JobManager.join, as the symptoms here are the same. Please reopen if you still experience on a build *after* 3.1 M3 (such as I20041111 or I20041117). *** This bug has been marked as a duplicate of 77039 ***
