In preparing an answer to your questions, I think I have discovered the problem.
I was building using an custom JDK image that I had modified slightly to work with the old packager. Using a released JDK 11, the bundled application starts fine. > On Apr 6, 2019, at 7:04 PM, Michael Hall <mik3h...@gmail.com> wrote: > > > >> On Apr 6, 2019, at 8:49 PM, Alan Snyder <javali...@cbfiddle.com> wrote: >> >> I have just tried using the latest jpackage release on macOS, after >> successfully using a very old sandbox version from long ago. >> Two command line argument names had to be changed, but otherwise the usage >> appears to be the same for my simple case of building a bundled app. >> However, the bundled app does not run. >> Executing the “main” executable from the terminal produces this output: >> >> Error: could not find libjava.dylib >> Error: Could not find Java SE Runtime Environment. >> >> The library exists in Contents/PlugIns/Java.runtime/Contents/Home/lib. >> > > What exactly are you entering to run the application? > > The full jpackage invocation parameters and output could be useful. > > >
