Bug 35081 - Breakpoints don't appear in nested type editor
Summary: Breakpoints don't appear in nested type editor
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 2.1   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.3   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-14 17:48 EST by Jared Burns CLA
Modified: 2007-06-12 05:00 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Burns CLA 2003-03-14 17:48:08 EST
Build 20030313

Breakpoints do not appear in editors for nested types. Neither breakpoints
set in the enclosing type's editor or breakpoints set in the nested type
editor show up.

1. Open type in AbstractTextEditor (from the binary plug-in).
2. Set a breakpoint anywhere in the file.
3. Open type on ActivationCodeTrigger. A separate editor opens for
AbstractTextEditor$ActivationCodeTrigger.
4. The breakpoint from step 2 does not appear.
Comment 1 Erich Gamma CLA 2003-03-16 11:56:55 EST
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.
Comment 2 Darin Wright CLA 2003-03-18 22:06:44 EST
Deferred
Comment 3 Darin Wright CLA 2003-04-09 12:30:53 EDT
re-open
Comment 4 Jared Burns CLA 2003-04-09 15:13:22 EDT
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?
Comment 5 Darin Wright CLA 2003-04-09 16:04:35 EDT
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.
Comment 6 Dani Megert CLA 2006-08-14 09:25:37 EDT
This has been fixed a while ago.