On 15 Oct 2014, at 16:52, Alan Bateman wrote:
> On 15/10/2014 16:09, Pavel Rappo wrote:
>> Hi everyone,
>>
>> Could you please review my change for JDK-8042888?
>>
>> http://cr.openjdk.java.net/~prappo/8042888/webrev.00/
>>
>>
> This looks good, you seem to have caught everything.
+1.
-Chr
On 15/10/2014 16:09, Pavel Rappo wrote:
Hi everyone,
Could you please review my change for JDK-8042888?
http://cr.openjdk.java.net/~prappo/8042888/webrev.00/
This looks good, you seem to have caught everything.
-Alan.
Hi everyone,
Could you please review my change for JDK-8042888?
http://cr.openjdk.java.net/~prappo/8042888/webrev.00/
Previously I sent an email to see if anyone uses this tool or has any thoughts
on its future [1].
--
On 11/09/2014 17:23, Pavel Rappo wrote:
:
We don't think it is widely used. And will become even less useful with
upcoming modularization. Are there any good reasons to keep this thing in the
JDK?
Searching for usages on stackoverflow and other sites doesn't come up
with much, it would be su
Hi everyone,
We are thinking of removing the extcheck tool. For those who doesn't remember
what it is, here is an extract from its man page:
extcheck(1)
NAME
extcheck - jar conflict detection utility
SYNOPSIS
extcheck [ -verbose ] [ -Joption ] targetfile.jar
DESCRIPTION
/extcheck/TestExtcheckArgs.java.sdiff.html
The test case will failed if run against the current jdk8 build image
because
all those jar files still have their "specification-version" listed as
"1.7", as
---
Manifest-Version: 1.0
Implement
Please help review the change at
http://cr.openjdk.java.net/~sherman/6907367/webrev
The proposed change does not include the test case I was originally planed
as showed at
http://cr.openjdk.java.net/~sherman/6907367/webrev.00/test/com/sun/tools/extcheck/TestExtcheckArgs.java.sdiff.html
The
