code-tools-dev Digest, Vol 32, Issue 1

Mani Sarkar sadhak001 at gmail.com
Sun Dec 3 17:02:46 UTC 2017


Thanks Jon for the jtreg enhancements, look forward to it's effect on the
adoptopenjdk code tools build farm.

On Sat, 2 Dec 2017 11:56 , <code-tools-dev-request at openjdk.java.net> wrote:

> Send code-tools-dev mailing list submissions to
>         code-tools-dev at openjdk.java.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mail.openjdk.java.net/mailman/listinfo/code-tools-dev
> or, via email, send a message with subject or body 'help' to
>         code-tools-dev-request at openjdk.java.net
>
> You can reach the person managing the list at
>         code-tools-dev-owner at openjdk.java.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of code-tools-dev digest..."
>
>
> Today's Topics:
>
>    1. RFR(XS): CODETOOLS-7902075: jtreg doesn't build if jh.jar
>       doesn't contain signatures (Volker Simonis)
>    2. Re: RFR(XS): CODETOOLS-7902075: jtreg doesn't build if jh.jar
>       doesn't contain signatures (Jonathan Gibbons)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 1 Dec 2017 17:29:44 +0100
> From: Volker Simonis <volker.simonis at gmail.com>
> To: code-tools-dev <code-tools-dev at openjdk.java.net>
> Subject: RFR(XS): CODETOOLS-7902075: jtreg doesn't build if jh.jar
>         doesn't contain signatures
> Message-ID:
>         <
> CA+3eh12X020bnrXe0Y0ngFnPqZC6xAwZSn4B_BiOtjSqGZqsWw at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi,
>
> can I please have a sponsor for the following simple fix of the jtreg
> build:
>
> http://cr.openjdk.java.net/~simonis/webrevs/2017/CODETOOLS-7902075/
> https://bugs.openjdk.java.net/browse/CODETOOLS-7902075
>
> Change "7901920: jh.jar is signed with a weak algorithm and its
> certificate is expired" introduced a logic to remove outdated
> signatures from jh.jar.
>
> However, there's no default location for downloading jh.jar and
> probably most available versions (e.g. the one from Maven:
>
> http://central.maven.org/maven2/javax/help/javahelp/2.0.05/javahelp-2.0.05.jar
> )
> if not all of them don't contain signatures at all. This breaks the
> build because removing the signatures from the jar file with zip will
> fail with the following error:
>
> zip warning: name not matched: META-INF/*.SF
> zip warning: name not matched: META-INF/*.RSA
> zip warning: name not matched: META-INF/*.DSA
> zip error: Nothing to do!
> (/net/usr.work/openjdk/tools/jtreg/jtreg/build/images/jtreg/lib/jh.jar
>
> It would be great if the sponsor could also tag this fix with
> jtreg4.2-b11 after pushing it because the last tagged version (i.e.
> jtreg4.2-b10) doesn't build out of the box without JCov (which should
> be optional and which was fixed by "7902072: Add support for imported
> license files").
>
> Thank you and best regards,
> Volker
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 01 Dec 2017 10:52:58 -0800
> From: Jonathan Gibbons <jonathan.gibbons at oracle.com>
> To: Volker Simonis <volker.simonis at gmail.com>, code-tools-dev
>         <code-tools-dev at openjdk.java.net>
> Subject: Re: RFR(XS): CODETOOLS-7902075: jtreg doesn't build if jh.jar
>         doesn't contain signatures
> Message-ID: <5A21A50A.7010509 at oracle.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Volker,
>
> I can push the fix for you, but it may already be redundant.
>
> If you use JT Harness 5, then you don't need JavaHelp at all.
> Just leave JAVAHELP_JAR unset.
>
> I've been pushing changes to jtreg this week to make it easier
> to build jtreg, and although I haven't yet flipped the switch on making
> the default be to use JT Harness 5, I have verified that you can
> build and run jtreg, using JT Harness 5, without JavaHelp and without
> JCov.
>
> -- Jon
>
> On 12/01/2017 08:29 AM, Volker Simonis wrote:
> > Hi,
> >
> > can I please have a sponsor for the following simple fix of the jtreg
> build:
> >
> > http://cr.openjdk.java.net/~simonis/webrevs/2017/CODETOOLS-7902075/
> > https://bugs.openjdk.java.net/browse/CODETOOLS-7902075
> >
> > Change "7901920: jh.jar is signed with a weak algorithm and its
> > certificate is expired" introduced a logic to remove outdated
> > signatures from jh.jar.
> >
> > However, there's no default location for downloading jh.jar and
> > probably most available versions (e.g. the one from Maven:
> >
> http://central.maven.org/maven2/javax/help/javahelp/2.0.05/javahelp-2.0.05.jar
> )
> > if not all of them don't contain signatures at all. This breaks the
> > build because removing the signatures from the jar file with zip will
> > fail with the following error:
> >
> > zip warning: name not matched: META-INF/*.SF
> > zip warning: name not matched: META-INF/*.RSA
> > zip warning: name not matched: META-INF/*.DSA
> > zip error: Nothing to do!
> > (/net/usr.work/openjdk/tools/jtreg/jtreg/build/images/jtreg/lib/jh.jar
> >
> > It would be great if the sponsor could also tag this fix with
> > jtreg4.2-b11 after pushing it because the last tagged version (i.e.
> > jtreg4.2-b10) doesn't build out of the box without JCov (which should
> > be optional and which was fixed by "7902072: Add support for imported
> > license files").
> >
> > Thank you and best regards,
> > Volker
>
>
>
> End of code-tools-dev Digest, Vol 32, Issue 1
> *********************************************
>
-- 

@theNeomatrix369 <http://twitter.com/theNeomatrix369>  |  Blog
<http://neomatrix369.wordpress.com/>  |  @adoptopenjdk | Dev communities

Meet-a-Project - MutabilityDetector <https://github.com/MutabilityDetector>
 |  Github <https://github.com/neomatrix369>  | Slideshare
<https://www.slideshare.net/neomatrix369>  | LinkedIn
<http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>

Come to Devoxx UK 2018: http://www.devoxx.co.uk/

Don't chase success, rather aim for "Excellence", and success will come
chasing after you!


More information about the code-tools-dev mailing list