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

Bug 36277

Summary:	Better marketing of encapsulate field [code manipulation] [refactoring]
Product:	[Eclipse Project] JDT	Reporter:	Oyvind Harboe <oyvind.harboe>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	preuss
Version:	2.1	Keywords:	usability
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Oyvind Harboe

2003-04-09 08:13:35 EDT

The "Source->Generate getter and setter method" is kinda obsolete.

If any code has been written at all, the user really should be 
considering "Refactoring->Encapsulate field".

The "Refactoring->Encapsulate field" should be better "marketed".

Possible action: retire "Source->Generate getter and setter method".



Øyvind

Comment 1 Ilja Preuss

2003-06-23 05:19:12 EDT

Downside: Generate Getter/Setter is much faster than Encapsulate Field.

Comment 2 Jason Yip

2004-02-26 17:19:35 EST

-1 on this one

I agree with Ilja that Generate getter and setter is faster in some cases which 
is why removing it just makes things less convenient.

Comment 3 Dirk Baeumer

2004-08-18 06:41:38 EDT

It is very unlikely that we can get rid of Generate Setter/Getter. Closing.