> On Sep 7, 2022, at 1:50 PM, Alexander Matveev <alexander.matv...@oracle.com> > wrote: > > Hi Michael, > > I file following issue for this: > https://bugs.openjdk.org/browse/JDK-8293462 > <https://bugs.openjdk.org/browse/JDK-8293462> > > Yes, you right it is related to JDK-8289030. I put suggested workaround to > https://bugs.openjdk.org/browse/JDK-8293462 > <https://bugs.openjdk.org/browse/JDK-8293462> in comment section. > > There are two possible workarounds: > 1) Generate signed application image initially, then post process it and sign > again. > 2) Generate unsigned application image and change value of <signed> from > false to true in "APPNAME.app/Contents/app/.jpackage.xml" and then do post > processing and sign it again. > > There is a bug in "jpackage --type app-image --app-image APPNAME.app > --mac-sign” command which signs app image correctly, but never changes value > in “.jpackage.xml” to mark image as signed. Thus we will treat such images as > unsigned even if they signed and as result we adding “.package” file when > generating DMG or PKG from such images. > > Thanks, > Alexander >
Alexander, Thanks for the reply. I hadn’t seen this. I have no immediate need for a work around. I will try to track the issue and wait on the fix before doing anything related. I saw you had filed a new one. I was just going to find that again when I saw this. Including the path to the .jpackage.xml file might be an idea if you are going to reference it in an error message. I hadn’t noticed mention of it before. Thanks, Mike
