Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312152 - NPE when close Eclipse
Summary: NPE when close Eclipse
Status: CLOSED DUPLICATE of bug 306537
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-08 06:33 EDT by Konstantin Scheglov CLA
Modified: 2010-05-11 16:56 EDT (History)
2 users (show)

See Also:

Attachments
Log (5.86 KB, application/octet-stream)
2010-05-08 06:37 EDT, Konstantin Scheglov 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 Konstantin Scheglov CLA 2010-05-08 06:33:34 EDT 
Build Identifier: 

I debug my plugin using sub-set of plugins from hosting Eclipse.
I've had already a lot of troubles with identifying why it does not work, even if I press "Add Required Plug-ins" button in launch configuration dialog. It seems that there are some implicit dependencies which can not by identified. I think that this is very bad, because now "Add Required Plug-ins" button is useless. For example equinox.ds always should be included, but HOW can I know this?

And after upgrading to 3.6M7 I stuck again. When I close Eclipse in logs NPE. I've added required plugins - still same exception. Can you tell me which plugins should be added? Or may be can you fix this NPE?

Reproducible: Always
Comment 1 Konstantin Scheglov CLA 2010-05-08 06:36:05 EDT 
Sorry, mixed up build and summary.
Build Identifier: I20100429-1549
Comment 2 Konstantin Scheglov CLA 2010-05-08 06:37:03 EDT 
Created attachment 167597 [details]
Log
Comment 3 Susan McCourt CLA 2010-05-08 10:49:30 EDT 
Konstantin, there was some discussion about "who should know that DS is needed?" in the newsgroup.
http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg06177.html

The answer is that the plug-ins can't establish this dependency because only the product configurer knows which implementation to use, etc.  We could, then, have PDE launch configs help detect this case...
Comment 4 Konstantin Scheglov CLA 2010-05-08 15:19:34 EDT 
Thank you for answer, Susan.
OK, now I understand why this happens.

Do you have idea what should be added to avoid NPE in this case?
Comment 5 Darin Wright CLA 2010-05-11 16:56:11 EDT 

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