Summary: | [breakpoints] improve conditional breakpoint error handling | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Darin Wright <darin.eclipse> |
Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | jared_burns, nickel.de |
Version: | 2.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Darin Wright
2003-02-04 14:41:41 EST
Deferred Consider for 3.0 I don't believe this is feasible since we moved to using property pages for breakpoints. Could we open the property page with a "red X" and error message? on the appropriate page, with the focus in the "condition" field? Agreed. This is now tricky, since we don't have easy access the property pages. We'd have to store the error on the breakpoint perhaps (as an attribute), and mark it with a red X? Deferred. reopening I'd like to see some suggestions for dependencies that should be added to fix a compilation error. Right now, I only see the error message "Conditional breakpoint has compilation error(s). Reason: The type org.eclipse.xyz.abc cannot be resolved. It is indirectly referenced from required .class files" But I haven't any clue where to add a dependency to org.eclipse.xyz.abc |