On Linux, when jpackage is invoked to build an app image, it attempts to run the "dpkg" command. This invocation is redundant and confusing.
Run jpackage on Debian Linux:
---
~/jdk-23.0.2/bin/jpackage -t app-image --input hello/ --main-jar hello.jar --main-class App -d ~/foo --runtime-image cooked-runtime --verbose
[17:27:25.300] Running dpkg
[17:27:25.445] Command [PID: 19388]:
dpkg --print-architecture
[17:27:25.445] Output:
amd64
[17:27:25.455] Returned: 0
[17:27:25.588] Creating app package: App in /home/asemenyu/foo
[17:27:25.647] Using default package resource JavaApp.png [icon] (add App.png to the resource-dir to customize).
[17:27:25.839] Succeeded in building Linux Application Image package
---
"[17:27:25.300] Running dpkg" indicates "dpkg" is being executed. This is redundant for app image packaging.
Run jpackage on Debian Linux:
---
~/jdk-23.0.2/bin/jpackage -t app-image --input hello/ --main-jar hello.jar --main-class App -d ~/foo --runtime-image cooked-runtime --verbose
[17:27:25.300] Running dpkg
[17:27:25.445] Command [PID: 19388]:
dpkg --print-architecture
[17:27:25.445] Output:
amd64
[17:27:25.455] Returned: 0
[17:27:25.588] Creating app package: App in /home/asemenyu/foo
[17:27:25.647] Using default package resource JavaApp.png [icon] (add App.png to the resource-dir to customize).
[17:27:25.839] Succeeded in building Linux Application Image package
---
"[17:27:25.300] Running dpkg" indicates "dpkg" is being executed. This is redundant for app image packaging.
- relates to
-
JDK-8333664 Decouple command line parsing and package building in jpackage
-
- Resolved
-