Bug 561607 - [Refactoring] The refactor move window is empty
Summary: [Refactoring] The refactor move window is empty
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.15   Edit
Hardware: Macintosh Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-31 05:16 EDT by LECOMTE Laurent CLA
Modified: 2024-03-13 13:13 EDT (History)
1 user (show)

See Also:

Attachments
The refactor window (empty) (57.63 KB, image/png)
2020-03-31 05:16 EDT, LECOMTE Laurent CLA 		no flags Details
same in preferences (123.92 KB, image/png)
2020-03-31 14:02 EDT, LECOMTE Laurent CLA 		no flags Details
View All 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 LECOMTE Laurent CLA 2020-03-31 05:16:37 EDT 
Created attachment 282283 [details]
The refactor window (empty)

I installer the lase version of eclipse and when I want to move a class to a package (refactor move) the windows supposed to show the packages avaible is empty
Comment 1 LECOMTE Laurent CLA 2020-03-31 14:02:54 EDT 
Created attachment 282294 [details]
same in preferences
Comment 2 Eclipse Genie CLA 2022-03-22 20:32:03 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-13 13:13:09 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.