Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342797 - [breakpoints] The position of breakpoint varies after refactoring java class name
Summary: [breakpoints] The position of breakpoint varies after refactoring java class ...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-14 03:55 EDT by Kentaroh Noji CLA
Modified: 2019-09-30 17:08 EDT (History)
4 users (show)

See Also:


Attachments
Screencapture (154.49 KB, image/png)
2011-04-14 04:00 EDT, Kentaroh Noji CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kentaroh Noji CLA 2011-04-14 03:55:33 EDT
Build Identifier: I20110407-2200

This bug was found and reported during DBCS enablement test, but this is not DBCS problem. 
The position of breakpoint in Java editor varied when I refactored the java class name. The problem occurs only if the refactored class name is longer than the original class name. This problem happens in both Eclipse v3.7 and v4.1.  

Reproducible: Always

Steps to Reproduce:
1.Create a Java project.
2.Create a Java class such as Abc.java
3.Add breakpoint into the the Abc.java
4.Select the Abc.java in the Package Explorer, then open the context menu. Then Refactor > Rename
5.Enter new class name. The class name must be longer than original name, e.g., Abcdef.java. Then Finish > Finish.
6.The position of breakpoint varies.
Comment 1 Kentaroh Noji CLA 2011-04-14 04:00:16 EDT
Created attachment 193223 [details]
Screencapture
Comment 2 Eclipse Genie CLA 2019-09-30 17:08:26 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.