ADDITIONAL SYSTEM INFORMATION :
openjdk 17.0.1, windows 10.
A DESCRIPTION OF THE PROBLEM :
When using jpackage to bundle an application the working directory is non-intuitive when invoked from shortcuts (Windows). There is no option in jpackage to change it, or it is poorly documented.
There should be an option to specify that the shortcuts should use the application root ('app' directory) and not the installation root as the working directory. All paths in the application that refer to the local filesystem are broken with the default shortcut working directory. The "app" parent folder is imposed by the jpackage bundler as it is not part of the working directory.
jpackage should be usable without having to insert a bundler-specific parent directory for all filesystem paths. This seems like a reasonable default behavior, however it should at least be configurable.
Related
https://bugs.openjdk.org/browse/JDK-8226904
https://bugs.openjdk.org/browse/JDK-8257979
openjdk 17.0.1, windows 10.
A DESCRIPTION OF THE PROBLEM :
When using jpackage to bundle an application the working directory is non-intuitive when invoked from shortcuts (Windows). There is no option in jpackage to change it, or it is poorly documented.
There should be an option to specify that the shortcuts should use the application root ('app' directory) and not the installation root as the working directory. All paths in the application that refer to the local filesystem are broken with the default shortcut working directory. The "app" parent folder is imposed by the jpackage bundler as it is not part of the working directory.
jpackage should be usable without having to insert a bundler-specific parent directory for all filesystem paths. This seems like a reasonable default behavior, however it should at least be configurable.
Related
https://bugs.openjdk.org/browse/JDK-8226904
https://bugs.openjdk.org/browse/JDK-8257979
- relates to
-
JDK-8226904 current working directory wrong running jpackage app
-
- Resolved
-
-
-
- Closed
-