Bug 561686 - Java conditional breakpoints does not get changed by java variable name refacrorings
Summary: Java conditional breakpoints does not get changed by java variable name refac...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.15   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-02 06:49 EDT by Olaf Bigalk CLA
Modified: 2024-03-18 03:09 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Bigalk CLA 2020-04-02 06:49:53 EDT 
Reproduce:
1. Define a variable in your java code
2. Use this variable in a breakpoint condition
3. Refactor the name of this variable
4. Run your code to hit the breakpoint

Result:
Error in conditional breakpoint: unknown variable.

Conlsusion:
The name of the variable has not been changed by the name refactoring(3.).

I did not check if this happens in other java refactorings that may affect conditional breakpoints. It has to be veryfied befor releasing a fix.
Comment 1 Sarika Sinha CLA 2020-04-02 07:14:49 EDT 
None of the refactoring takes care of conditional breakpoints.

We don't plan to work on this right now, if any one interested please provide a quality patch.
Comment 2 Eclipse Genie CLA 2022-03-24 07:12:50 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 3 Eclipse Genie CLA 2024-03-18 03:09:59 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.