Skip to content

8356128: Correct documentation for --linux-package-deps #23638

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

Conversation

StefanLobbenmeier
Copy link
Contributor

@StefanLobbenmeier StefanLobbenmeier commented Feb 14, 2025

The documentation suggests that --linux-package-deps is a boolean option, while in fact it is a string option with dependencies separated by comma and space

You can tell that this option is supposed to have an argument here:

private static final BundlerParamInfo<String> LINUX_PACKAGE_DEPENDENCIES =
new StandardBundlerParam<>(
Arguments.CLIOptions.LINUX_PACKAGE_DEPENDENCIES.getId(),
String.class,
params -> "",
(s, p) -> s
);


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8356128: Correct documentation for --linux-package-deps (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 23638

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Feb 14, 2025
@bridgekeeper
Copy link

bridgekeeper bot commented Feb 14, 2025

Hi @StefanLobbenmeier, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user StefanLobbenmeier" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@openjdk
Copy link

openjdk bot commented Feb 14, 2025

@StefanLobbenmeier 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:

8356128: Correct documentation for --linux-package-deps

Reviewed-by: asemenyuk, 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 1713 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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@alexeysemenyukoracle, @sashamatveev) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk
Copy link

openjdk bot commented Feb 14, 2025

@StefanLobbenmeier 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.

@StefanLobbenmeier
Copy link
Contributor Author

/signed

@bridgekeeper bridgekeeper bot added the oca-verify Needs verification of OCA signatory status label Feb 14, 2025
@bridgekeeper
Copy link

bridgekeeper bot commented Feb 14, 2025

Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

@StefanLobbenmeier
Copy link
Contributor Author

See also JetBrains/compose-multiplatform#5227 for a discussion if this option has an argument

@bridgekeeper
Copy link

bridgekeeper bot commented Mar 14, 2025

@StefanLobbenmeier This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@StefanLobbenmeier
Copy link
Contributor Author

Just gonna try /signed again, but I didn’t get any more information from oracle

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 12, 2025

@StefanLobbenmeier This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@bridgekeeper bridgekeeper bot removed oca Needs verification of OCA signatory status oca-verify Needs verification of OCA signatory status labels Apr 29, 2025
@StefanLobbenmeier
Copy link
Contributor Author

StefanLobbenmeier commented May 1, 2025

a new comment
I guess the action also suggests that i should first create a Jira issue

@StefanLobbenmeier StefanLobbenmeier changed the title Correct documentation for --linux-package-deps 9078456: Correct documentation for --linux-package-deps May 1, 2025
@StefanLobbenmeier
Copy link
Contributor Author

Cannot do that, but I could create a but to oracle jdk so I used that review id

@StefanLobbenmeier StefanLobbenmeier changed the title 9078456: Correct documentation for --linux-package-deps 8356128: Correct documentation for --linux-package-deps May 5, 2025
@openjdk openjdk bot added the rfr Pull request is ready for review label May 5, 2025
@mlbridge
Copy link

mlbridge bot commented May 5, 2025

Webrevs

@StefanLobbenmeier
Copy link
Contributor Author

Also maybe one follow up question - what do I need to do so the change appears in older versions like

@alexeysemenyukoracle
Copy link
Member

Thank you for making the change! Other property files and jpackage.md should also be updated to sync them with HelpResources.properties.

@alexeysemenyukoracle
Copy link
Member

alexeysemenyukoracle commented May 21, 2025

Also maybe one follow up question - what do I need to do so the change appears in older versions like

You need to backport this fix once it is integrated. See https://openjdk.org/guide/#backporting

@StefanLobbenmeier
Copy link
Contributor Author

Thank you for making the change! Other property files and jpackage.md should also be updated to sync them with HelpResources.properties.

Done, sorry I missed them

@alexeysemenyukoracle
Copy link
Member

Looks good!

@alexeysemenyukoracle
Copy link
Member

@StefanLobbenmeier, if you would like to have this fix in JDK25, you need to issue the /integrate command in the PR. I'll sponsor it. The entire sequence should be completed by the end of June 4th; otherwise, this fix will be included in JDK26.

@StefanLobbenmeier
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Jun 3, 2025

@StefanLobbenmeier This pull request has not yet been marked as ready for integration.

@StefanLobbenmeier
Copy link
Contributor Author

There is an integration blocker because of the issue title, should I change the PR or can you change the issue title?

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jun 3, 2025
@alexeysemenyukoracle
Copy link
Member

I've updated the title in the JBS record. Please try to integrate.

@StefanLobbenmeier
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jun 3, 2025
@openjdk
Copy link

openjdk bot commented Jun 3, 2025

@StefanLobbenmeier
Your change (at version 51ed08e) is now ready to be sponsored by a Committer.

@alexeysemenyukoracle
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Jun 3, 2025

Going to push as commit cc11b7d.
Since your change was applied there have been 1715 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 Jun 3, 2025
@openjdk openjdk bot closed this Jun 3, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Jun 3, 2025
@openjdk
Copy link

openjdk bot commented Jun 3, 2025

@alexeysemenyukoracle @StefanLobbenmeier Pushed as commit cc11b7d.

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

@StefanLobbenmeier
Copy link
Contributor Author

Thank you very much for sponsoring ❤️

@alexeysemenyukoracle
Copy link
Member

No problem. Thank you for your contribution!

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.

3 participants