This module contains both pack200 and unpack200 tools although it only
contains the native implementation of unpacker. Naming it as
jdk.unpack200 would give an impression that it contains the unpacker
only which isn't the case.
Like the API java.util.jar.Pack200 class, it's about Pack200
On 2015-03-05 10:25, Erik Joelsson wrote:
Hello Mandy,
The build changes look ok to me.
Build changes are OK for me too.
/Magnus
/Erik
On 2015-03-05 02:13, Mandy Chung wrote:
As listed in an open issue in JEP 200:
The jdk.dev and jdk.runtime modules contain miscellaneous tools that do
On Mar 6, 2015, at 01:55, Mandy Chung mandy.ch...@oracle.com wrote:
For this review request, are you okay with this patch moving policytool and
jarsigner tools to the new home?
Yes.
--Max
On 05/03/2015 01:13, Mandy Chung wrote:
:
Separate webrevs for each issue:
1. pack200, unpack200 to jdk.pack200
http://cr.openjdk.java.net/~mchung/jdk9/webrevs/8074428%2b8074429%2b8074430/8074428/webrev.00/
I think this looks okay. In the unshuffle_list (for back/forward porting
patches)
On 5 Mar 2015, at 08:31, Alan Bateman alan.bate...@oracle.com wrote:
On 05/03/2015 01:13, Mandy Chung wrote:
:
Separate webrevs for each issue:
1. pack200, unpack200 to jdk.pack200
http://cr.openjdk.java.net/~mchung/jdk9/webrevs/8074428%2b8074429%2b8074430/8074428/webrev.00/
I think
On 05/03/2015 01:13, Mandy Chung wrote:
3. policytool to jdk.policytool
http://cr.openjdk.java.net/~mchung/jdk9/webrevs/8074428%2b8074429%2b8074430/8074430/webrev.00/
This part looks good to me.
-Alan
On 05/03/2015 01:13, Mandy Chung wrote:
:
2. jar, jarsigner to jdk.jartool
http://cr.openjdk.java.net/~mchung/jdk9/webrevs/8074428%2b8074429%2b8074430/8074429/webrev.00/
It seems reasonable to have both jar and jarsigner in the same module so
I think this is good. This will also work if
On 3/5/2015 12:31 AM, Alan Bateman wrote:
On 05/03/2015 01:13, Mandy Chung wrote:
:
Separate webrevs for each issue:
1. pack200, unpack200 to jdk.pack200
http://cr.openjdk.java.net/~mchung/jdk9/webrevs/8074428%2b8074429%2b8074430/8074428/webrev.00/
I think this looks okay. In the
Hello Mandy,
The build changes look ok to me.
/Erik
On 2015-03-05 02:13, Mandy Chung wrote:
As listed in an open issue in JEP 200:
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
I am about to introduce 2 APIs into jdk.dev so that people can call functions
of keytool and jarsigner directly. So what I am suggesting is
- Create jdk.security.util
- Move jarsigner, policytool to jdk.security.util
- Create the new APIs in this module
- Move keytool to jdk.security.util, it's
On 3/4/2015 6:55 PM, Wang Weijun wrote:
I am about to introduce 2 APIs into jdk.dev so that people can call functions
of keytool and jarsigner directly.
Are you referring to these 2 RFEs?
https://bugs.openjdk.java.net/browse/JDK-8056174
https://bugs.openjdk.java.net/browse/JDK-8058778
We
As listed in an open issue in JEP 200:
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.
Currently there are jdk.javadoc, jdk.jconsole, jdk.jcmd modules in
the JDK that
12 matches
Mail list logo
