JDK-8029548 : (jdeps) use @jdk.Exported to determine supported vs JDK internal API
- Type: Enhancement
- Component: tools
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2013-12-04
- Updated: 2015-01-21
- Resolved: 2014-07-09
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 | JDK 9 |
|---|---|
8u40Fixed  |
9 b23Fixed |
Related Reports
|
Relates :
|
Description
The current implementation of jdeps reads ct.sym to determine if it is supported or JDK internal API. ct.sym is only generated for rt.jar and for the image build. This doesn't cover the APIs in tools.jar nor other classes not in rt.jar. In JDK 9, jigsaw will modularize the platform and declare exported APIs in the module metadata. The enhancement in jdeps should take that into account.