> On Sep 26, 2022, at 9:24 PM, Michael Hall <mik3h...@gmail.com> wrote: > > > >> On Sep 20, 2022, at 5:50 PM, Michael Hall <mik3h...@gmail.com >> <mailto:mik3h...@gmail.com>> wrote: >> >> 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. > > 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? > > I then remembered > > [macos]: App bundle cannot upload to Mac App Store due to info.plist embedded > in java exe > https://bugs.openjdk.org/browse/JDK-8286122 > <https://bugs.openjdk.org/browse/JDK-8286122> >
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. 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.
