jpackage does not include extra files from app-image when creating Debian package?

[Michael Hall]

> On Feb 27, 2021, at 11:05 AM, Tobias Oelgarte <tobias.oelgarte at gmail.com> wrote:
> 
> This works. Thank you very much.
> -
> Sadly i have to copy the files to different image app folder locations, depending on the operating system. Under Windows it is 'image/AppName/app/' and under Linux it is 'image/AppName/lib/app'. Would have been nice if all images would have the same directory structure. This way i have to create OS specific maven profiles.
> 
> On 27.02.21 14:42, Andy Herrick wrote:
>> If you want to find the app dir directly on all platforms, use a command line option as Michael does in HalfPipe, except directly:
>> 
>> --java-options -Djpackage.app.dir='$APPDIR'
>> 
>> this $APPDIR will be expanded when jli is invoked to point to the applications app dir. ($BINDIR, and $ROOTDIR can be used in similar ways)
>> 
>> /Andy
>> 

I noticed the Windows version of my app was out of date. Other fixes seemed necessary. So I decided to re-do all my builds.

Exception in thread "main" java.lang.UnsatisfiedLinkError: no hp in java.library.path: /opt/ooRexx/lib/ooRexx:/Users/mjh/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
	at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source)
	at java.base/java.lang.Runtime.loadLibrary0(Unknown Source)
	at java.base/java.lang.System.loadLibrary(Unknown Source)
	at us.hall.osx.LogOut.<clinit>(LogOut.java:9)
	at us.hall.hp.common.LoaderLaunchStub.main(LoaderLaunchStub.java:59)

It does seem there is some kind of regression on java.library.path where it doesn’t do the application specific internal paths anymore.
-Djava.library.path=$APPDIR
Seems a work around.
You might have a bug report there. I don’t think I can do one.

jpackage --version
WARNING: Using incubator modules: jdk.incubator.jpackage
15.0.2