Re: [External] : Re: RFR: 8286122: [macos]: App bundle cannot upload to Mac App Store due to info.plist embedded in java exe

> On May 17, 2022, at 12:15 AM, Alexander Matveev > wrote: > > Hi Michael, > > I filed following enhancement for signing user provided app image and yes it > will be two step process. Invoke jpackage to generate image, then user can > modified it and then invoke jpackage again to sign it.

Re: [External] : Re: RFR: 8286122: [macos]: App bundle cannot upload to Mac App Store due to info.plist embedded in java exe

Hi Michael, I filed following enhancement for signing user provided app image and yes it will be two step process. Invoke jpackage to generate image, then user can modified it and then invoke jpackage again to sign it. https://bugs.openjdk.java.net/browse/JDK-8286850 For JDK-8286122, I will int

Re: [External] : Re: RFR: 8286122: [macos]: App bundle cannot upload to Mac App Store due to info.plist embedded in java exe

> On May 16, 2022, at 7:09 PM, Alexander Matveev > wrote: > > Hi Michael, > >> I’m not real familiar with the build process. But would it be possible for the user to build their own jdk that substitutes something else for the colliding identifier that gets embedded? >

Re: [External] : Re: RFR: 8286122: [macos]: App bundle cannot upload to Mac App Store due to info.plist embedded in java exe

Hi Michael, > >>> >>> I’m not real familiar with the build process. But would it be possible for >>> the user to build their own jdk that substitutes something else for the >>> colliding identifier that gets embedded? >> Yes, it should be possible and in theory such JDK with native commands ca