Bug 32959

Summary:	[quick fix] "Change visibility of xxx to protected" QFs should offer all possible visibilities
Product:	[Eclipse Project] JDT	Reporter:	Andre Weinand <andre_weinand>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	daniel_megert, martinae
Version:	2.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Andre Weinand

2003-02-25 09:41:51 EST

RC1

Whenever a QF "Change visibility of xxx to protected" is proposed, all other possible 
"visibilities" should be proposed too.
One example is the explicit call to "super()" if the base class constructor is private.

Comment 1 Dirk Baeumer

2003-02-26 12:30:55 EST

Martin, do we get a hint from core the protected is sufficient.

Comment 2 Martin Aeschlimann

2003-02-26 12:39:30 EST

no, i just chose the minimal visiblility possible that solves the problem.
We have to see if there aren't too many proposals if we offer them all.

Comment 3 Dirk Baeumer

2003-02-27 10:28:38 EST

Not critical for 2.1

Comment 4 Dani Megert

2009-06-22 05:03:33 EDT

Comment 5 rgra Missing name

2012-11-20 12:38:04 EST

This would break a number of test-cases which count the number of proposals.