| Summary: | Breakpoints don't appear in nested type editor | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jared Burns <jared_burns> |
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | darin.eclipse |
| Version: | 2.1 | ||
| Target Milestone: | 3.3 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jared Burns
Opening another editor for a nested type is not ideal and we should revisit this in JDT text. However, this cannot happen for 2.1. Deferred re-open Is there anything Debug can do to facilitate this? I thought we just create a marker. Isn't it the nested type editor's responsibility to render the markers from the resource of the enclosing type? I believe this is up to JUI/Text. Breakpoints in outer types only appear on the outer type editor (for class files), and breakpoints on inner types only appear in the editor for the inner type. This is due to the fact that the breakpoint marker has an association with a specific type. Moving to JUI. This has been fixed a while ago. |