Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 36943

Summary:	[plan item] Provide API for refactoring
Product:	[Eclipse Project] JDT	Reporter:	Jim des Rivieres <jeem>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	burner, crivet, danrubel, duongn, m.a.r.k, n.a.edgar, richkulp, robert.simmons, taciano
Version:	2.1	Keywords:	plan
Target Milestone:	3.0
Hardware:	All
OS:	All
Whiteboard:

Description Jim des Rivieres

2003-04-25 17:48:06 EDT

Provide API for refactoring. JDT should allow other plug-ins to contribute 
specialized refactoring operations, and provide the infrastructure to make it 
possible for them to do so. [JDT Core, JDT UI]

Comment 1 Miguel A Paraz

2003-06-15 12:09:51 EDT

I think this API can also support source generation, and not just refactoring
current code. 

For instance, one operation I'd like to use (and code) would be "generate a
constructor that initializes all final fields with parameters." This is a
repetitive task if you have a lot of value objects in your project.

Comment 2 John Arthorne

2003-07-31 12:31:31 EDT

*** Bug 13530 has been marked as a duplicate of this bug. ***

Comment 3 Richard Kulp

2003-07-31 14:34:56 EDT

For us (Visual Editor for Java) an important API that needs to be opened up is
the capability of renaming an variable within a method. Currently this is done
through source range and is an internal API. We thank you for already opening up
the rename of an IField. We use that and it works great. But we also need to
rename variables. Source ranges is sufficient, just we need it as API. Thanks.

Comment 4 Dirk Baeumer

2003-10-24 07:58:18 EDT

*** Bug 45493 has been marked as a duplicate of this bug. ***

Comment 5 Dirk Baeumer

2004-06-25 11:23:18 EDT

With 3.0 there are two new plug-ins available, ltk.refactoring.core and 
ltk.refactoring.ui which allows clients to implement their won refactorings 
using the same infrastructure.

The goal of this PR wasn't to make more JDT/UI refactorings API. I opened bug 
68625 for comment #3.