I have found a way to do this but am not happy with it:
field PC = AWS EC2 instance and headless/legless field PC
1. upload C:\java\jdk-11.0.1 from development PC to each field PC - a one time expense so this is OK
2. on development PC, for each production B4J module, just create its release jar - don't do the B4JPackager11 stuff - end up with MYB4JPGM.jar
3. upload each MYB4JPGM.jar to appropriate field PCs (say to D:\MYB4JPGM\MYB4JPGM.jar) - small so no problem
4. upload C:\Program Files (x86)\Anywhere Software\B4J\release_java_modules.txt from development PC to appropriate field PCs (say to D:\MYB4JPGM\release_java_modules.txt)
4. on each field PC, copy C:\java\jdk-11.0.1\java.exe to C:\java\jdk-11.0.1\MYB4JPGM.exe
5. on each field PC, launch MYB4JPGM with this launch command:
C:\java\jdk-11.0.1\bin\MYB4JPGM.exe @D:\MYB4JPGM\release_java_modules.txt -p C:\java\jdk-11.0.1\javafx\lib -jar D:\MYB4JPGM\MYB4JPGM.jar
this results in the Restart On Crash tool being able to see MYB4JPGM (actually the renamed/copied java.exe)
The thing I don't like about it is all the various MYB4JPGM.exe accumulating in C:\java\jdk-11.0.1\
I'd much prefer to have them in D:\MYB4JPGM with the like named jar - but I can not for the life of me work out how to modify the launch command to something like:
D:\MYB4JPGM\MYB4JPGM.exe @D:\MYB4JPGM\release_java_modules.txt -p C:\java\jdk-11.0.1\javafx\lib -jar D:\MYB4JPGM\MYB4JPGM.jar
I need a parameter to tell java.exe/MYB4JPGM.exe to look in C:\java\jdk-11.0.1\bin for all its bits.
Any suggestions?