Bug 402507

Summary: [rename] refactor action inactive on last character of variable in Javadoc
Product: [Eclipse Project] JDT Reporter: Nicolas Bros <nicolas.bros>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert
Version: 3.7.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Nicolas Bros CLA 2013-03-06 04:58:48 EST
With the following code:
  /** @param abc */
  public void test(final int abc) {
    ...
  }

I noticed that when I place the cursor right after "abc" in the javadoc comment and I try to invoke "Refactor > Rename...", then nothing happens. Whereas if I place my cursor in the middle of the name or right before it in the javadoc then the action works. 

This is an inconsistency because if I place my cursor right after "abc" in the method definition then the action works.
Comment 1 Eclipse Genie CLA 2019-04-02 15:41:47 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 Dani Megert CLA 2019-04-03 04:49:59 EDT
Still broken in 4.11.
Comment 3 Eclipse Genie CLA 2021-03-24 15:03:44 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 4 Eclipse Genie CLA 2023-05-27 05:30: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.