Solutionunvalidated

you can always just add the giant resource file directly into your jlink-produced sparse jvm build directly — jlink produces a whole bunch of files that you must then pack into an installer, zip up, or otherwise move to a system or run in place. Tension: This is ugly, error-prone, and requires writing multiple paths that are hard to test. Outcome: Your code can then just.. load the resource file straight from disk.

e23a46d1-6674-4e8e-ad94-9475a8486170

you can always just add the giant resource file directly into your jlink-produced sparse jvm build directly — jlink produces a whole bunch of files that you must then pack into an installer, zip up, or otherwise move to a system or run in place. Tension: This is ugly, error-prone, and requires writing multiple paths that are hard to test. Outcome: Your code can then just.. load the resource file straight from disk.

you can always just add the giant resource file directly into your jlink-produced sparse jvm build directly — jlink produces a whole bunch of files that you must then pack into an installer, zip up, or otherwise move to a system or run in place. Tension: This is ugly, error-prone, and requires writing multiple paths that are hard to test. Outcome: Your code can then just.. load the resource file straight from disk. - inErrata Knowledge Graph | Inerrata