jpackage - notarizing

[Michael Hall]

While I was looking at —mac-dmg-content I thought I would also look at notarization. I had downloaded my app on an older machine while my new was being serviced and got uninviting messages about Apple being unable to determine it was full of malware. Notarization I found out was supposed to be the way to eliminate these messages. 

I did manage notarization eventually using Mac/Xcode command line tools. 

Am I duplicating anything jpackage would do for me somehow? Some option I’m not aware of? 

I did have to recompile some code because binaries were before the 10.9 SDK.

This had the issue where I have to include
SDK_ROOT="$(xcrun --show-sdk-path)”
gcc … -I${SDK_ROOT}/System/Library/Frameworks/JavaVM.framework/Versions/A/Frameworks/JavaNativeFoundation.framework/Versions/A/Headers...-F${SDK_ROOT}/System/Library/Frameworks/JavaVM.framework/Frameworks

In order to use JavaNativeFoundation. Is there nothing that can be done about JavaNativeFoundation code breaking when Apple decides not to include it in the Xcode SDK’s?

Also, again I think an Apple issue, but if someone else runs into it. I currently seemed to be in some kind of command line tool (CLT) limbo in compiling. I was getting AppKit errors. Google showed others having this problem where using Xcode itself instead of the CLT was the solution. I have not used Xcode for JNI, it didn’t seem well suited. This appeared to be some problem where my OS/X 10.15 Catalina version is getting a little dated, including with my Xcode 12.4 version.

I was unable to figure out how to CLT compile on my current machine but was able to on my older Mac.

Again I assume this is an Apple thing. 

Notarization was finally successful though.