Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

alexeysemenyukoracle
Copy link
Member

@alexeysemenyukoracle alexeysemenyukoracle commented Aug 8, 2025

  • 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.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Change requires CSR request JDK-8364656 to be approved
  • Commit message must refer to an issue

Warning

 ⚠️ Found leading lowercase letter in issue title for 8308349: missing working directory option for launcher when invoked from shortcuts

Issues

  • JDK-8308349: missing working directory option for launcher when invoked from shortcuts (Enhancement - P4)
  • JDK-8364656: missing working directory option for launcher when invoked from shortcuts (CSR)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26707/head:pull/26707
$ git checkout pull/26707

Update a local copy of the PR:
$ git checkout pull/26707
$ git pull https://git.openjdk.org/jdk.git pull/26707/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26707

View PR using the GUI difftool:
$ git pr show -t 26707

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26707.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Aug 8, 2025

👋 Welcome back asemenyuk! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Aug 8, 2025

@alexeysemenyukoracle This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

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

Reviewed-by: almatvee

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 21 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk
Copy link

openjdk bot commented Aug 8, 2025

@alexeysemenyukoracle The following label will be automatically applied to this pull request:

  • core-libs

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added core-libs [email protected] rfr Pull request is ready for review labels Aug 8, 2025
@mlbridge
Copy link

mlbridge bot commented Aug 8, 2025

Webrevs

private static boolean hasNextArg() {
return context().pos < context().argList.size();
}

private static Runnable createArgumentWithOptionalValueAction(String option) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure, but did you test case when --win-menu or --win-shortcut or --linux-shortcut is last argument without value? With new code var value = popArg(); will be "" and we will call setOptionValue(option, value). Before change it will be set to true.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. I reworked the tests, and they start failing if the last argument is --win-menu, --win-shortcut, or --linux-shortcut.

Copy link
Member

@sashamatveev sashamatveev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Aug 11, 2025
…ch one of the additional launchers is started when invoked through a shortcut.
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Aug 12, 2025
@alexeysemenyukoracle
Copy link
Member Author

@sashamatveev, please review again. This is the final iteration.

@@ -85,14 +92,16 @@

public class AddLShortcutTest {

@Test
@Test(ifNotOS = OperatingSystem.MACOS)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need both (ifNotOS = OperatingSystem.MACOS) and (os.family != "mac")?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The one is for jtreg, and the other is for the jpackage test runner. The latter makes sense when the test is executed outside of jtreg.

Copy link
Member

@sashamatveev sashamatveev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Latest changes looks good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Aug 12, 2025
@alexeysemenyukoracle
Copy link
Member Author

/integrate

@openjdk
Copy link

openjdk bot commented Aug 12, 2025

Going to push as commit 72d3a2a9773b2a3fe0351e0acb7b10c0751d23d8.
Since your change was applied there have been 21 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Aug 12, 2025
@openjdk openjdk bot closed this Aug 12, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Aug 12, 2025
@openjdk
Copy link

openjdk bot commented Aug 12, 2025

@alexeysemenyukoracle Pushed as commit 72d3a2a.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-libs [email protected] integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

2 participants