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
8256299: Implement JEP 396: Strongly Encapsulate JDK Internals by Default #1324
Conversation
👋 Welcome back mr! A progress list of the required criteria for merging this PR into |
@mbreinhold The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
/label jigsaw, core-libs |
@mbreinhold The label
|
/csr |
@mbreinhold the issue for this pull request, JDK-8256299, already has an approved CSR request: JDK-8256300 |
Webrevs
|
@mbreinhold 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 341 new commits pushed to the
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 |
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 hostpot change is trivially fine.
I'm somewhat surprised by the extent of the other changes given the basic change here is to deprecate the option and change its default. I literally expected to see only 2 simple changes to the functional code: the deprecation warning and the changing of the default value.
There are interactions with the archiving of the module graph and boot layer. Here's one of the mails from the review of JDK-8244778 that has more context: |
Mailing list message from David Holmes on hotspot-runtime-dev: Hi Alan, On 20/11/2020 6:04 pm, Alan Bateman wrote:
Thanks for the information. I don't understand enough to know why this Cheers, |
…nExportedPackage test This reverts commit 6a4d479.
…dPackage test (v2)
/contributor add alanb |
@mbreinhold |
/integrate |
@mbreinhold Since your change was applied there have been 341 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit ed4c4ee. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this implementation of JEP 396 (https://openjdk.java.net/jeps/396).
Alan Bateman is the original author; I’ve credited him in the commit metadata.
Passes tiers 1-3 on {linux,macos,windows}-x64 and linux-aarch64.
Progress
Issue
Reviewers
Contributors
<alanb@openjdk.org>
Download
$ git fetch https://git.openjdk.java.net/jdk pull/1324/head:pull/1324
$ git checkout pull/1324