On 07/10/2019 08:00, David Holmes wrote:
On 7/10/2019 4:43 pm, Alan Bateman wrote:
On 07/10/2019 04:35, David Holmes wrote:
Nothing to do with jpackage but a fix to Class.forName to ensure
classes are linked as per the specification of forName. You can
temporarily workaround with -XX:+ClassForNameDeferLinking, but your
code needs to be updated to deal with LinkageErrors from Class.forName.
In this case, it is core reflection code that it looking at the type
parameters in the type of a field. I suspect this code needs to
translate NCDEF to TypeNotPresentException, other linkage errors
maybe need to be handled here too.
Oops! Yes indeed.
I've created JDK-8231924 [1] to track this. We will need to a wider
audit of Class.forName usages in the JDK in case there are other issues
like this.
-Alan
[1] https://bugs.openjdk.java.net/browse/JDK-8231924
