Bug 267936 - Make IJDIPreferencesConstants API
Summary: Make IJDIPreferencesConstants API
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks: 267642
  Show dependency tree
 
Reported: 2009-03-10 14:19 EDT by Diego Madruga Sandin CLA
Modified: 2009-03-11 09:56 EDT (History)
4 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 Diego Madruga Sandin CLA 2009-03-10 14:19:48 EDT 
The class org.eclipse.jdt.internal.debug.ui.IJDIPreferencesConstants is marked as internal.

MTJ uses this class to automatically configure the default JDI request timeout value using the JDIDebugModel.PREF_REQUEST_TIMEOUT constant.

Could IJDIPreferencesConstants be considered for inclusion in the JDT UI API?
Comment 1 Dani Megert CLA 2009-03-11 03:37:24 EDT 
>Could IJDIPreferencesConstants be considered for inclusion in the JDT UI API?
This is in JDT Debug.
Comment 2 Darin Wright CLA 2009-03-11 09:30:02 EDT 
I don't understand the request. JDIDebugModel.PREF_REQUEST_TIMEOUT is API - how/why do you need to use the internal constants?
Comment 3 Diego Madruga Sandin CLA 2009-03-11 09:45:27 EDT 
Sorry, I've put the wrong constant in the bug report.

We are actually using JDIPreferencesConstants.PREF_SUSPEND_ON_UNCAUGHT_EXCEPTIONS and JDIPreferencesConstants.PREF_SUSPEND_ON_COMPILATION_ERRORS to configure the debugger settings to correctly work with mobile sdks.

Is there a way to programaticaly configure this preferences without using this constants?
Comment 4 Darin Wright CLA 2009-03-11 09:56:54 EDT 
Currently, there is no API for these settings. Looking at the implementation, it should probably be improved if an API is required. The debug target itself should have options to control whether to suspend on compilation errors/exceptions. Currently, this is acheived via preferences and the UI plug-in which creates associated breakpoints.

As the API freeze is upon us, this won't be done until a later release.