Bug 264279 - [common navigator][dnd] Drag/drop to (default project) incorrect copies instead of moves
Summary: [common navigator][dnd] Drag/drop to (default project) incorrect copies inste...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 298652 (view as bug list)
Depends on:
Blocks: 209537
  Show dependency tree
 
Reported: 2009-02-09 19:16 EST by Francis Upton IV CLA
Modified: 2022-08-23 04:49 EDT (History)
3 users (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 Francis Upton IV CLA 2009-02-09 19:16:50 EST 
HEAD (with a couple of patches)

1) Have a java project, with a non-default package and a class
2) Drag the class to the (default package)
--->>  It will copy, and not move.  The package explorer correctly moves.

The patches are:

bug 263845 (fix the "sticking" copy issue)
bug 209537 (JavaDropAdapterAssistent uses stale selection)
Comment 1 Dani Megert CLA 2009-02-10 02:28:22 EST 

*** This bug has been marked as a duplicate of bug 209537 ***
Comment 2 Dani Megert CLA 2010-01-08 04:49:03 EST 
Actually not fixed (neither 3.5.x nor HEAD).
Comment 3 Dani Megert CLA 2010-01-08 04:49:19 EST 
*** Bug 298652 has been marked as a duplicate of this bug. ***
Comment 4 Eclipse Genie CLA 2020-07-09 05:56:41 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 5 Eclipse Genie CLA 2022-08-23 04:49:23 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.