From victor.rudometov at oracle.com  Wed Oct  2 21:42:37 2019
From: victor.rudometov at oracle.com (victor.rudometov at oracle.com)
Date: Wed, 02 Oct 2019 21:42:37 +0000
Subject: hg: code-tools/sigtest: CODETOOLS-7902521 Sigtest does not clear
 parameters between runs
Message-ID: <201910022142.x92Lgb25025473@aojmv0008.oracle.com>

Changeset: f12b94c4ba3f
Author:    vrudomet
Date:      2019-10-02 14:42 -0700
URL:       https://hg.openjdk.java.net/code-tools/sigtest/rev/f12b94c4ba3f

CODETOOLS-7902521 Sigtest does not clear parameters between runs

! src/classes/com/sun/tdk/signaturetest/SignatureTest.java


From ross.goldberg at gmail.com  Wed Oct  9 09:38:08 2019
From: ross.goldberg at gmail.com (Ross Goldberg)
Date: Wed, 9 Oct 2019 05:38:08 -0400
Subject: Tool to determine if all Java bytecode dependencies are properly
 satisfied
Message-ID: <CAAEcvMpOAZPAL=grafyC497b1y1MQSMmPEXrL7Lbj5CtzMyvYw@mail.gmail.com>

Is there any tool that, for a list of jars (and/or class files), reports
when any Java bytecode dependencies are not satisfied either from those
jars and/or classes, or from jars and/or classes on a class path or module
path (e.g., missing types, methods, constructors, and/or fields)?

Obviously, a compiler does this for source, but I want it for bytecode.  I
want to determine which versions of third-party jars are signature
compatible with my jars.

If any such tools exist, are any smart / flexile enough to handle code
generated from annotations, and/or reflection based on statically-known
information (e.g., using a constant String for reflection)?

Thanks.