Bug 392528 - [dnd] Reordering enum constants in the outline causes constructor arguments to be discarded
Summary: [dnd] Reordering enum constants in the outline causes constructor arguments t...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-21 12:43 EDT by Bill Chen CLA
Modified: 2022-07-02 15:19 EDT (History)
2 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 Bill Chen CLA 2012-10-21 12:43:34 EDT 
Using       Eclipse Java Development Tools	3.8.1.v20120814-104540-8-8nFqpFNOfwKDRVz-tXOcL5d_83	org.eclipse.jdt.feature.group

Steps to reproduce:
1. Create an enum with a private constructor with arguments
2. Create some enum items calling the constructor
3. Drag one enum item to another position

Expected:
The constructor arguments on the item should still be there.

Actual:
The arguments are gone.
Comment 1 Dani Megert CLA 2012-10-22 08:33:53 EDT 
Move one of the constants to see the problem:

enum Test {
	T1(), T2(), T3();
}
Comment 2 Eclipse Genie CLA 2020-07-01 13:58:49 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 2022-07-02 15:19:38 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.