Bug 55216 - Generalize Type should tell me why generalization is not possible [refactoring]
Summary: Generalize Type should tell me why generalization is not possible [refactoring]
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Frank Tip CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-18 09:04 EST by Markus Keller CLA
Modified: 2008-12-01 09:57 EST (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 Markus Keller CLA 2004-03-18 09:04:21 EST 
When a supertype is grayed out in the Generalize Type dialog, the user doesn't
know why the generalization to that type is not possible.

One deeply burried method call can be enough to prevent the refactoring, and
when the user is informed about that, he can remove it and proceed. I imagine an
"Advanced" button which shows the offending usages for each disabled supertype.
Comment 1 Dirk Baeumer CLA 2004-03-19 06:41:14 EST 
Frank, I like this idea. What do you think ?
Comment 2 Frank Tip CLA 2004-03-19 21:41:50 EST 
I agree this is a good idea. Generalize Type is currently considering
only one declaration at the time, so it's not hard to generate "reasons"
why a declaration cannot be generalized. I will put this on my to-do list.

  -Frank