JDK-8072601 : Re-examine jdk.runtime and jdk.dev modules
  • Type: Task
  • Component: core-libs
  • Sub-Component: java.lang.module
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-02-05
  • Updated: 2017-01-19
  • Resolved: 2015-06-02
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.
JDK 9
9Fixed
Related Reports
Blocks :  
Blocks :  
Blocks :  
Relates :  
Relates :  
Sub Tasks
JDK-8074428 :  
JDK-8074429 :  
JDK-8074430 :  
JDK-8074432 :  
Description
One of the remaining issues in JEP 200 is:

The jdk.dev and jdk.runtime modules contain miscellaneous tools that do not obviously belong to any other module; these modules will eventually be either renamed or refactored.
Comments
This task is completed. jimage in jdk.dev is temporary and jdk.dev will be removed completely when the module system is integrated to jdk9.
02-06-2015

jdk.javadoc, jdk.jconsole, jdk.jcmd modules are organized around its primary tool which is easy to name, document, and understand. Hence the current proposal for the tools in jdk.runtime and jdk.dev modules will be organized as follows: pack200, unpack200, libpack200.so -> jdk.pack200 jar, jarsigner -> jdk.jartool jdeps -> jdk.compiler policytool -> jdk.policytool -> /dev/null in JDK 10 if not JDK 9 native2ascii -> /dev/null
04-03-2015