[External] : Re: jpackage - notarizing

[Alan Snyder]

> On Nov 22, 2021, at 7:01 PM, Kevin Rushforth <kevin.rushforth at oracle.com> wrote:
> 
> By way of clarification, JNF was never part of the JDK. What we removed was the JDK's *usage* of JNF. And we did so because Apple deprecated it and never even provide a JNF framework for aarch64.
> 
> Applications either need to migrate off JNF and find an alternative, or take Apple's open-source project, build it yourself, and include it with your application. Either way, this isn't a JDK problem.
> 
> -- Kevin
> 


Except for the multiple UI thread coordination issue, which is most definitely a JDK issue, as it is a direct consequence of AWT/Swing using its own UI event thread instead of using the AppKit main thread.

See: https://bugs.openjdk.java.net/browse/JDK-8270211




> 
> On 11/22/2021 11:56 AM, Michael Hall wrote:
>> 
>>> On Nov 22, 2021, at 12:39 PM, Alan Snyder <javalists at cbfiddle.com> wrote:
>>> 
>>> 
>>>> On Nov 22, 2021, at 10:12 AM, Kevin Rushforth <kevin.rushforth at oracle.com> wrote:
>>>> 
>>>> JNF was removed from the JDK if that's what you are asking.
>>> 
>>> 
>>> Indeed, that is why there is an issue.
>>> 
>>> The JDK may not be using JNF, but library developers still use it.
>>> 
>>> The JDK replacement for JNF is not supported for use outside the JDK.
>>> 
>>> JNF is not just convenient, there is at least one essential use for which there is no adequate replacement.
>>> 
>>> See https://bugs.openjdk.java.net/browse/JDK-8274596
>>> 
>>> 
>>> 
>> I have a fair amount of code that would break if some JNF option wasn’t available. I have no estimate for how much rewriting I would need to do. Two of the projects I needed to recompile to get notarized needed it. I don’t actively do anything with it anymore but have some older code that did.
>> 
>