Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 36256

Summary: Crash when running closed project has bad error message
Product: [Eclipse Project] Platform Reporter: Paul E. Keyser <rolarenfan>
Component: DebugAssignee: Platform-Debug-Inbox <platform-debug-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 2.0.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Paul E. Keyser CLA 2003-04-08 17:29:59 EDT
R2.0.2, Win2K

User, not being an eclipse-guru, has both a plugin project and an SWT
project in his workspace.  User runs the SWT project, stops it, closes
the SWT project.  After a long enough break that user forgot what
exactly he had last done, user foolishly presses F11, thinking it will
run the runtime-ws-and-plugin; instead, gets this error message:

An exception occurred while launching

Reason:
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object

After some while, realises that F11 is now trying to run a closed
project (I would have thought that such an action would either have been
prevented -- closing a project should remove it from the "run stack" or
whatever it's called -- or would have crashed sooner with a message like
"Cannot run closed Project 'YouDoofus'").
Comment 1 Darin Wright CLA 2003-04-08 22:23:42 EDT

*** This bug has been marked as a duplicate of 19521 ***