Integrated: 8308349: missing working directory option for launcher when invoked from shortcuts

Alexey Semenyuk asemenyuk at openjdk.org
Tue Aug 12 03:19:17 UTC 2025


On Fri, 8 Aug 2025 22:37:21 GMT, Alexey Semenyuk <asemenyuk at openjdk.org> wrote:

> - Support a new "app-dir" value of `win-shortcut`, `win-menu`, and `linux-shortcut` properties in additional launcher property files.
> - Support an optional value of `--win-shortcut`, `--win-menu`, and `--linux-shortcut` CLI options. The valid value is "app-dir".
> 
> If a value of any property/CLI option from the above list is set to "app-dir", the startup directory of the corresponding shortcut will be set to the "app" subdirectory of the installation directory.
> 
> If a CLI option from the above list doesn't have a value, the startup directory of the corresponding shortcut for the main launcher will be set to the installation directory on Windows and will not be set on Linux. This is the existing behavior; it has not changed.
> 
> If a value of a property from the above list evaluates to `true`, the startup directory of the corresponding shortcut for the additional launcher will be set to the installation directory on Windows and will not be set on Linux. This is the existing behavior; it has not changed.
> 
> Added test cases to AddLShortcut test implicitly.
> 
> Reworked one of the additional launchers in AddLShortcut.test() to allow verification of the working directory when the launcher is invoked through the shortcut in manual tests.

This pull request has now been integrated.

Changeset: 72d3a2a9
Author:    Alexey Semenyuk <asemenyuk at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/72d3a2a9773b2a3fe0351e0acb7b10c0751d23d8
Stats:     372 lines in 16 files changed: 272 ins; 28 del; 72 mod

8308349: missing working directory option for launcher when invoked from shortcuts

Reviewed-by: almatvee

-------------

PR: https://git.openjdk.org/jdk/pull/26707


More information about the core-libs-dev mailing list