Bug 15979 - error restart Eclipse after opening update manager
Summary: error restart Eclipse after opening update manager
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Update (deprecated - use Eclipse>Equinox>p2) (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Vlad Klicnik CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 15970 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-05-14 17:25 EDT by Jim des Rivieres CLA
Modified: 2002-05-17 14:36 EDT (History)
5 users (show)

See Also:

Attachments
.log showing NPE (7.22 KB, text/plain)
2002-05-14 17:26 EDT, Jim des Rivieres CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jim des Rivieres CLA 2002-05-14 17:25:39 EDT 
Integration build 20020514

0. Fresh install; fresh workspace
1. Launch eclipse.exe
2. Open update manager
3. Exit eclipse

4. Launch eclipse.exe

Observe: Error "Unable to read workbench state. workbench.xml will be deleted."

See attached .log showing NPE near
org.eclipse.update.internal.model.InstallConfigurationModel.initialize
Comment 1 Jim des Rivieres CLA 2002-05-14 17:26:27 EDT 
Created attachment 815 [details]
.log showing NPE
Comment 2 Vlad Klicnik CLA 2002-05-14 19:06:35 EDT 
I am currently chasing this one ... as funny as this sounds, the NPE is being 
caused by our plugin not being activated despite the fact we are executing its 
classes. I have traced runtime class loading in detail and the trace shows the 
org.eclipse.update.core loader loading classes from updatecore.jar, BUT the 
plugin is never activated. The trace also shows the org.eclipse.update.ui 
plugin being activated twice !!!!???
Comment 3 Jim des Rivieres CLA 2002-05-14 19:22:38 EDT 
This is the second case of out-of-order plug-in activation I've heard about in 
the last 5 minutes!

What changes went in to core.runtime that could have cause this?
Comment 4 Vlad Klicnik CLA 2002-05-14 19:34:08 EDT 
I do not know .... nothing from our end.
Comment 5 Rodrigo Peretti CLA 2002-05-14 21:37:55 EDT 
*** Bug 15970 has been marked as a duplicate of this bug. ***
Comment 6 Nick Edgar CLA 2002-05-14 22:58:32 EDT 
The exceptions shown here should not have caused us to fail startup.
It should have continued even though it could not create the Configuration 
view.
The first stack was caught and handled by an ISafeRunnable.  The second one 
was in the ViewPane code, caused by the first failure, but it was not caught.
I've added the necessary checks in Pane and ViewPane.
Comment 7 Vlad Klicnik CLA 2002-05-17 14:36:59 EDT 
Was caused by bogus class loader change.