JDK-8003562 : Provide a command-line tool to find static dependencies
- Type: Bug
- Component: tools
- Affected Version: 8
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2012-11-16
- Updated: 2017-05-17
- Resolved: 2012-12-29
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 |
|---|
8 b73Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
As proposed in http://openjdk.java.net/jeps/162, add a tool to analyze class dependencies to help developers prepare for the modular platform. Provide a command-line tool in the JDK so that developers can understand the static dependencies of their applications and libraries ��� As part of Project Jigsaw, a useful class analyzer was developed that makes it very easy to identify the dependencies. This class analyzer will be modified to make it easy to identify the usage of non-standard and JDK internal APIs and would provide a useful complement to the warnings emitted by javac when compiling code that make use of JDK internal APIs.