jpackage does not include extra files from app-image when creating Debian package?
mik3hall at gmail.com
Sat Feb 27 14:37:43 UTC 2021
> On Feb 27, 2021, at 5:51 AM, Tobias Oelgarte <tobias.oelgarte at gmail.com> wrote:
> On 27.02.21 11:22, Michael Hall wrote:
>>> On Feb 27, 2021, at 1:31 AM, Tobias Oelgarte <tobias.oelgarte at gmail.com> wrote:
>>>> No, there is no platform independent and reliable way to get the path to 'app' directory. However you can get location of one of your app's classes through Class.getResource(). See https://stackoverflow.com/questions/227486/find-where-java-class-is-loaded-from <https://stackoverflow.com/questions/227486/find-where-java-class-is-loaded-from>
>>> That isn't helpful at all. All i get is either the URL jrt:/<modulename> or null, but not the installation directory or something similar.
>> System property? java.home, java.launcher.path, java.library.path, java.class.path
> java.library.path is a list of paths pointing outside of the application directory. For example: '/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib’
Andy’s suggestion seems good.
Is all internal to the application. I notice it includes app. I’m not quite sure how it picks up the wekafiles/native.
More information about the jdk-dev