Bug 264546 - [breakpoints] Doubleclick on ruler in annotate editor on old revision should not toggle breakpoint
Summary: [breakpoints] Doubleclick on ruler in annotate editor on old revision should ...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-11 11:39 EST by Markus Keller CLA
Modified: 2023-02-15 11:55 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2009-02-11 11:39:34 EST
I20090203-1200

Doubleclick on ruler in annotate editor on old revision should not toggle breakpoint.

Steps:
- check out org.eclipse.core.expressions from CVS
- open class org.eclipse.core.internal.expressions.CompositeExpression
- Show In > History view
- on revision 1.1, choose context menu > Show Annotation
- on line 33, doubleclick on line number or in the left ruler

=> A breakpoint is added, but it only shows up in the Breakpoints view, and not in the ruler: "CompositeExpression [line: 33] - CompositeExpression". The breakpoint also does not show up in the editor for the current version, but it does suspend a thread when execution enters that line.

=> Expected: Breakpoint should only be toggled if the editor is for the file in the workspace.

What's strange is that the breakpoint is not added if I open revision 1.1 without showing CVS annotations.
Comment 1 Eclipse Genie CLA 2020-06-17 15:47:45 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-02-15 11:55:49 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.