jdk17u-dev
jdk17u-dev copied to clipboard
8286447: [Linux] AWT should start in Headless mode if headful AWT library not installed
Backport applied cleanly.
Progress
- [x] Change must not contain extraneous whitespace
- [x] Commit message must refer to an issue
- [ ] Change requires CSR request JDK-8324306 to be approved
- [ ] JDK-8286447 needs maintainer approval
Issues
- JDK-8286447: [Linux] AWT should start in Headless mode if headful AWT library not installed (Enhancement - P4)
- JDK-8324306: [Linux] AWT should start in Headless mode if headful AWT library not installed (CSR)
Reviewing
Using git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2150/head:pull/2150
$ git checkout pull/2150
Update a local copy of the PR:
$ git checkout pull/2150
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2150/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2150
View PR using the GUI difftool:
$ git pr show -t 2150
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2150.diff
Webrev
:wave: Welcome back luhenry! 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.
This backport pull request has now been updated with issue from the original commit.
⚠️ @luhenry This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.
/csr needed
@luhenry has indicated that a compatibility and specification (CSR) request is needed for this pull request.
@luhenry please create a CSR request for issue JDK-8286447 with the correct fix version. This pull request cannot be integrated until the CSR request is approved.
@GoeLin What would be the next steps after creating the CSR? I'm sorry it's a process that's very new to me. Thanks for your help!
@luhenry 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!
❗ This change is not yet ready to be integrated. See the Progress checklist in the description for automated requirements.
@luhenry 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!
@luhenry This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.