Bug 102322 - [typing] False compile error after move method, undo move, same move method again.
Summary: [typing] False compile error after move method, undo move, same move method a...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-30 10:24 EDT by Brian Miller CLA
Modified: 2022-06-28 15:48 EDT (History)
0 users

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 Brian Miller CLA 2005-06-30 10:24:54 EDT 
Bug 94619 is fixed, but its problem can still be caused with additional 
interaction.  Do the Refactor>>Move described in bug 94619.  The false error 
no longer appears the first time, but then do Edit>>UndoMoveMember (Ctrl+Z), 
and then explicitly do the Refactor>>Move again (don't use Ctrl+Y).  This 
causes the false error.

I'm using I20050627.
Comment 1 Eclipse Genie CLA 2020-06-04 14:49:13 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 2022-06-28 15:48:00 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.