JDK-8071338 : Move policytool from JRE to JDK
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-01-22
  • Updated: 2017-05-17
  • Resolved: 2015-02-13
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
9 b52Fixed
Related Reports
Blocks :  
JDK-8072601 - Re-examine jdk.runtime and jdk.dev modules
Description
Policytool is a seldomly used GUI tool for editing policy files. Most users have no need to edit policy files. This issue proposes moving it from the jdk.runtime to the jdk.dev module so it is only included in the JDK, and not the JRE.
Comments
Release note for JDK-8147400 will cover this change.
19-01-2017
Release note: Policy Tool is moved from JRE into JDK.
05-02-2015
We need to find a home for pack200. We need to revisit jdk.runtime module name. com.sun.tracing will be removed. The question for policytool is whether we want to keep policytool and then which module it's the appropriate home for it. If it will stay in JRE, another option is to have its own module (jdk.policytool). jdk.dev (its name needs to be revisited as well) includes several other JDK tools and if policytool can be moved to JDK, jdk.dev is one possible home for it.
23-01-2015
Was there a reason why it got added into jdk.runtime? The name "runtime" sounds like some sort of library or infrastructure or environment but policytool is an executable that no other depends on. Also, I see pack200 there, is that also a tool or really a runtime lib?
23-01-2015