Bug 32959 - [quick fix] "Change visibility of xxx to protected" QFs should offer all possible visibilities
Summary: [quick fix] "Change visibility of xxx to protected" QFs should offer all poss...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-25 09:41 EST by Andre Weinand CLA
Modified: 2012-11-20 12:38 EST (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 Andre Weinand CLA 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 CLA 2003-02-26 12:30:55 EST 
Martin, do we get a hint from core the protected is sufficient.
Comment 2 Martin Aeschlimann CLA 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 CLA 2003-02-27 10:28:38 EST 
Not critical for 2.1
Comment 4 Dani Megert CLA 2009-06-22 05:03:33 EDT 
.
Comment 5 rgra Missing name CLA 2012-11-20 12:38:04 EST 
This would break a number of test-cases which count the number of proposals.