Re: [jdt-debug-dev] Promote BreakpointUtils to API

[Darin_Wright@xxxxxxx]

I disagree with this proposal. The methods/utils in BreakpointUtils are specific to the Java Debug UI. The Java Debug UI has "built" new breakpoint types out of the breakpoint supplied by the java debug (core) plug-in. The "run-to-line" breakpoint is specific to the java debug UI, as well as the "problem breakpoint". The java debug ui annotates these breakpoints with attributes to identify them as such.

As well, the breakpoint creation API was made more general by creating breakpoints based on type names (rather than java model types). The Java Debug UI has utilities for determining the java model type/member associated with breakpoints, but this too, is specific to the java debug UI, and is not required by core.

Darin

Jared Burns <jared-eclipse@xxxxxxxxx> Sent by: jdt-debug-dev-admin@xxxxxxxxxxx 02/25/2002 10:35 AM Please respond to jdt-debug-dev

To:        jdt-debug-dev@xxxxxxxxxxx         cc:                 Subject:        [jdt-debug-dev] Promote BreakpointUtils to API

org.eclipse.jdt.internal.debug.ui.BreakpointUtils should be moved to the jdt 
debug core, renamed to JavaBreakpointUtils, and promoted to API 
(org.eclipse.jdt.debug.JavaBreakpointUtils).

The methods on this "class" were once part of the API in the IJavaBreakpoint 
hierarchy. When they were pulled out of the hierarchy (to seperate the 
breakpoint hierarchy from the java model), they were also moved to the UI 
component. However, these methods are still useful in the core. As such, this 
functionality should be returned to the core and promoted to API so that the 
UI can still access them.

- Jared
_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-debug-dev