Stubbornly insisting on using JLINK for deployment

I’ve managed to write a working self-contained .exe for deployment, using the tool javapackager. I’m resisting deploying because I’d like to use the smaller runtime I made with JLINK.

The documentation on this is really difficult, imho. Maybe I am just being too stubborn (e.g., just package the complete runtime, or, learn ANT and try to follow the documentation on that path instead of javapackager).

Question for the more experienced folks at JGO:

  1. How bad is it to have an app be, say, 180MB instead of 80MB? The app itself has a lightweight feel to it–maybe comprises 3MB of code. Are people who are willing to try plunking down $3 or $4 say going to be okay with this project size? (Down the road, I have some projects I was going to aim at $1. Will having a full JRE selfcontained with each be a problem for something this “small”?)

  2. Does anyone happen to know if javapackager is even capable of deploying a jlink-generated runtime? (If you can answer this, consider also answering my question at Stack Overflow. Or, I can transfer the info over.)

So much whoop-de-do in books on Safari online about how the jlink runtime runs faster, can be used for more efficient deployments, etc., but I am unable to find one that details the actual deployment process for Windows (or any OS). And the “official” guide is a difficult read, confusingly organized, and relies deeply on Ant.

(SIDE ISSUE: Not entirely clear to me even how to use the .exe yet–the deployment guide and tutorials I have found don’t give examples–they assume people already know that? But what if this is your first time? My result includes ToneCircleDrone-1.0.exe and a file folder with src and runtime. Now what?)

:clue:

Thanks for any help.