<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 26, 2022, at 9:24 PM, Michael Hall <<a href="mailto:mik3hall@gmail.com" class="">mik3hall@gmail.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=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Sep 20, 2022, at 5:50 PM, Michael Hall <<a href="mailto:mik3hall@gmail.com" class="">mik3hall@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Still you could use post-processing to add whatever java binary executable commands you wanted. This again would mean changes to the embedded jdk that might have signing side effects. I haven’t tested. </span></div></blockquote><br class=""></div><div class="">Thinking about this I looked at my application that includes java commands and saw that currently I include all. And all appear to be of fixed size. So I assume some kind of launcher stub?</div><div class=""><br class=""></div><div class="">I then remembered </div><div class=""><br class=""></div><div class="">[macos]: App bundle cannot upload to Mac App Store due to info.plist embedded in java exe</div><div class=""><a href="https://bugs.openjdk.org/browse/JDK-8286122" class="">https://bugs.openjdk.org/browse/JDK-8286122</a></div><div class=""><br class=""></div></div></div></blockquote><br class=""></div><div>It might be an idea, if coming up with a unique or hashed CFBundleIdentifier in the Info.plist isn’t seen as a workable alternative, for jpackage to issue a warning anytime jlink parameters are passed without —strip-native-commands to issue a warning message that the application will not be eligible for the Mac App Store. </div><div>So developers don’t develop applications with a dependency on native commands intending them for the Mac App Store only to find out when they attempt a final MAS version that they are prohibited.</div><br class=""></body></html>