Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 431300 - [extract method] Extract method involving EnumConstantDeclaration is not handled correctly
Summary: [extract method] Extract method involving EnumConstantDeclaration is not hand...
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 486440 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-03-26 21:43 EDT by Martin Mathew CLA
Modified: 2020-04-27 03:18 EDT (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 Martin Mathew CLA 2014-03-26 21:43:13 EDT 
package p1;

class Constants {
	static final String EXT2_CLASS = ".class";
	
	enum Replacer2 {
		TEST("s"), // [1] Invoke Extract Method for "s"
		NILL1(EXT2_CLASS), NILL2(Constants.EXT2_CLASS);
		
		String s;
		
		
		Replacer2(String s) {
			this.s = "s"; // [2] Invoke Extract Method for "s"
		}
	}
}
In the case of [1] extract method reports an error saying "Cannot extract new method since the selection is not valid."

In the case of [2] though the dialog says 1 additional occurrence will be replaced, except the selected instance no other instance is updated with the extracted method.
Comment 1 Noopur Gupta CLA 2016-01-27 07:30:31 EST 
*** Bug 486440 has been marked as a duplicate of this bug. ***
Comment 2 Eclipse Genie CLA 2020-04-26 05:07:45 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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 leokom leokom CLA 2020-04-27 02:14:02 EDT 
The bug is already not reproduced in Eclipse 2020-03