<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 7, 2022, at 1:50 PM, Alexander Matveev <<a href="mailto:alexander.matveev@oracle.com" class="">alexander.matveev@oracle.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi Michael,
<div class=""><br class="">
</div>
<div class="">I file following issue for this:</div>
<div class=""><a href="https://bugs.openjdk.org/browse/JDK-8293462" class="">https://bugs.openjdk.org/browse/JDK-8293462</a></div>
<div class=""><br class="">
</div>
<div class="">Yes, you right it is related to JDK-8289030. I put suggested workaround to <a href="https://bugs.openjdk.org/browse/JDK-8293462" class="">https://bugs.openjdk.org/browse/JDK-8293462</a> in comment section.</div>
<div class=""><br class="">
</div>
<div class="">There are two possible workarounds:</div>
<div class="">1) Generate signed application image initially, then post process it and sign again.</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class="">Alexander<br class="">
<div class=""><br class="">
</div></div></div></div></blockquote><br class=""></div><div>Alexander,</div><div><br class=""></div><div>Thanks for the reply. I hadn’t seen this.</div><div>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.</div><div>I saw you had filed a new one. I was just going to find that again when I saw this.</div><div>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.</div><div><br class=""></div><div>Thanks,</div><div>Mike</div><br class=""></body></html>