Bug 578752 - [refactoring] Drag&drop of package to other package in hierarchical package representation should be equivalent to refactoring
Summary: [refactoring] Drag&drop of package to other package in hierarchical package r...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.22   Edit
Hardware: PC Windows 10
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: ui, usability
Depends on:
Blocks:
 
Reported: 2022-02-14 17:04 EST by Dirk Steinkamp CLA
Modified: 2024-02-05 00:29 EST (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 Dirk Steinkamp CLA 2022-02-14 17:04:53 EST 
Given:
- package or project explorer with package presentation set to hierarchical
- classes residing in package a.x
- another (possibly empty) package a.y

When:
- drag&drop sub-package x to a.y

Then:
- eclipse initiates a copy operation (reporting a name conflict with package a.x and proposing a.x.copy as destination package name), but should perform a rename package refactoring with destination package "a.y.x"

(a copy operation should only be initiated when drag&drop-operation is executed with ctrl-key pressed)
Comment 1 Eclipse Genie CLA 2024-02-05 00:29:10 EST 
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.