-
Notifications
You must be signed in to change notification settings - Fork 5.8k
JDK-8273229: Update OS detection code to recognize Windows Server 2022 #5347
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
👋 Welcome back mbaesken! A progress list of the required criteria for merging this PR into |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link to the "Windows Server release information" page is useful to check the build number - thanks!
@MBaesken 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:
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 10 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Matthias,
Some minor suggestions but okay as-is.
Thanks,
David
* Windows Server 2022 10 0 (!VER_NT_WORKSTATION) | ||
* where (buildNumber > 20347) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a comment at line 392 that you may want to adjust too - perhaps just say "Windows Server 2016+" to avoid the need to keep updating it.
// distinguish Windows Server 2016, 2019 and 2022 by build number | ||
// Windows server 2019 GA 10/2018 build number is 17763 | ||
if (build_number > 17762) { | ||
// Windows server 2022 build number is 20348 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps to avoid too much future editing:
// Distinguish Windows Server by build number:
// - 2016 GA 10/2016 build: 14393
// - 2019 GA 11/2018 build: 17763
// - 2022 GA 08/2021 build: 20348
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi David , thanks for your suggestions. I adjusted the comments.
Best regards, Matthias
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates
/integrate |
Going to push as commit c2e015c.
Your commit was automatically rebased without conflicts. |
Hello, please review this small change.
The OS detection code of the JDK/JVM should recognize the new Windows server 2022 :
https://docs.microsoft.com/en-us/lifecycle/products/windows-server-2022
https://docs.microsoft.com/en-us/windows-server/get-started/windows-server-release-info
The build number of Windows server 2022 according to the documentation in the second link is 20348 .
Thanks, Matthias
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5347/head:pull/5347
$ git checkout pull/5347
Update a local copy of the PR:
$ git checkout pull/5347
$ git pull https://git.openjdk.java.net/jdk pull/5347/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5347
View PR using the GUI difftool:
$ git pr show -t 5347
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5347.diff