Bug 444815 - Checkbox in Type Hierarchy for exported classpath only
Summary: Checkbox in Type Hierarchy for exported classpath only
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-23 06:43 EDT by Peter CLA
Modified: 2014-09-23 06:43 EDT (History)
0 users

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 Peter CLA 2014-09-23 06:43:37 EDT 
If you write a 2rd party library you may like to reduce the Types you offer to a 3rd party. But the hierarchy shows them all, known in the project if they are exported or not.

Because:

The type hierarchy helps by finding a best-matching type in example, but you may only like offer a type that:
1. match your needs of information you like to offer the 3rd party.
2. can be handled by an 3rd level library.

This is a complex process i think because it must respect the project-dependencies and their exports. Even if the JRE/JDK is not selected as "exported" those classes shall NOT be appear in the hierarchy (anyway: to decide to have the JRE/JDK exported is meaningless in my point-of-view).

Extra:

This helps people in complex frameworks (like using large maven-dependencies) to find some generic-exceptions in example.