> On Jan 20, 2022, at 9:23 AM, Steve Hannah <st...@weblite.ca> wrote:
>
> My reason for a launcher is that I'm building an alternative to jpackage that
> uses npm for deployment/versioning/updates and allows you to build native
> bundles for all platforms (Mac/Linux/Windows) on any platform. I.e. You
> don't need to be building on a Windows box to create a native windows exe.
> You don't need to worry about Mac codesigning and notarization, etc... It
> just takes care of all that for you on whatever system you're developing on.
>
> I already had it working well but it currently launches JVM in a separate
> process which wasn't optimal - so I'm working on improving it to be able to
> run in the same process as the launcher. This (I think) was the last
> obstacle.
>
> Best regards
>
> Steve
I’m not sure jpackage handles the notarization. I had done it for a jpackage
application and posted something on how to do it on my site. My builds are
currently throwing some sort of error on that I haven’t looked at yet. The code
signing and packaging I think all invoke native OS/X commands. Not trivial but
that could also probably be done on your own. It appeared tricky with an
already signed embedded jdk. It took jpackage a few releases to get it right.
>
> On Thu, Jan 20, 2022 at 7:13 AM Michael Hall <mik3h...@gmail.com
> <mailto:mik3h...@gmail.com>> wrote:
>
>
> > On Jan 20, 2022, at 9:08 AM, Steve Hannah <st...@weblite.ca
> > <mailto:st...@weblite.ca>> wrote:
> >
> > I just wanted to post an update on this in case it helps some future dev
> > who gets stuck on the same issue.
> >
>
> You probably have good reasons for having your own launcher but you might
> want to consider if jpackage could be an alternative and let that handle
> these cross-platform application details.
>
>
>
