Review Request: 8074428, 8074429, 8074430 jdk.pack200, jdk.jartool, jdk.policytool modules

Weijun Wang at
Thu Mar 5 09:13:19 UTC 2015

There is no problem the new API be in a separate module. It is 
independent of keytool now.

Said that, I've been thinking about rewriting keytool to use this new API.


On 3/5/2015 16:23, Alan Bateman wrote:
> On 05/03/2015 02:55, Wang Weijun wrote:
>> - Move keytool to, it's now in java.base but keytool
>> is not part of Java SE spec (Of course, if that means keytool will be
>> in JDK instead of JRE please stop. But will there will the name
>> difference anymore? I am thinking of an installer like cygwin that you
>> can choose anything except that java.base is checked grayed).
> The reason that keytool is in java.base is so that keys and certificates
> can be managed on a small runtime. It's the same reason that it is in
> our compact1 builds too. I wasn't aware of JDK-8058778 but it can't
> result in java.base exporting a JDK-specific API.
> -Alan

More information about the security-dev mailing list