Bug 116413 - [ErrorHandling][Preferences] Improved error messages for using PreferencePages
Summary: [ErrorHandling][Preferences] Improved error messages for using PreferencePages
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-15 04:50 EST by Thilo Brause CLA
Modified: 2019-09-06 16:09 EDT (History)
2 users (show)

See Also:

Attachments
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 Thilo Brause CLA 2005-11-15 04:50:43 EST 
When doing anything wrong with a Preference Page, at selecting the faulty page
under "Preferences" nearly always lead to the message:" Unable to create the
selected PreferencePage Reason: .... Plugin was unable to load class
...Preference Page". In most cases this error message leads into a complete
wrong direction of error-searching and debugging. Maybe it would be possible to
throw exceptions with better error messages, for example the error in my case
was produced by an error in the ..Plugin.java. (And I spend a day searching in
my PreferencePage and the calling classes)
Comment 1 Susan McCourt CLA 2009-07-09 19:04:30 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 2 Dina Sayed CLA 2009-09-24 07:59:34 EDT 
I don't know how to reproduce this scenario, can you explain it in more details and attach a screen shot if possible?
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:46 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.