-
Notifications
You must be signed in to change notification settings - Fork 534
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
[build] Build with Microsoft OpenJDK 21.0.5 #9683
base: main
Are you sure you want to change the base?
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Copilot reviewed 5 out of 8 changed files in this pull request and generated no comments.
Files not reviewed (3)
- build-tools/xaprepare/xaprepare/Steps/Step_InstallAdoptOpenJDK.cs: Evaluated as low risk
- build-tools/automation/yaml-templates/variables.yaml: Evaluated as low risk
- build-tools/xaprepare/xaprepare/Steps/Step_GenerateFiles.cs: Evaluated as low risk
For those of us out of the loop, can you elaborate on what this means for our customers and our CI?
Once committed, anything that is new for .NET 10 should be documented here: #9571. |
|
Context: #9651
Context: 14a6bfb
Updates the macOS, Windows, and Linux build stages to install and build with Microsoft OpenJDK 21.0.5.
The nightly test jobs have also been updated to use JDK 21, while all other test jobs should continue to use JDK 17.
As of 14a6bfb, main/.NET 10 supports both JDK 17 and 21.
The default version that VS and the
InstallAndroidDependencies
target will install is JDK 17, though we may want to upgrade this to 21 as we move further into the .NET 10 cycle.As of this PR, all explicit test stages that run against regular PR/CI will continue to use JDK 17. The build jobs, Windows smoke tests, and nightly test jobs will build and test against JDK 21. JDK 11 support was technically removed in df68c20, though I believe customers can add
<MinimumSupportedJavaVersion>11.0</MinimumSupportedJavaVersion>
to their project files to use it. Some test coverage for this exists in ValidateJavaVersionTests, but this scenario is not tested end to end.