Bug 444815

Summary:	Checkbox in Type Hierarchy for exported classpath only
Product:	[Eclipse Project] JDT	Reporter:	Peter <p.rader>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	4.5
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Peter

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.