-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
8265248: Implementation Specific Properties: change prefix, plus add existing properties #3644
Conversation
…existing properties
👋 Welcome back joehw! A progress list of the required criteria for merging this PR into |
@JoeWang-Java The following label 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 list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
/csr |
@JoeWang-Java this pull request will not be integrated until the CSR request JDK-8265252 for issue JDK-8265248 has been approved. |
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.
Good morning Joe,
The changes look good based on the discussions we have had about the change and the property documentation is more convenient to find
try { | ||
int temp; | ||
if (Integer.class.isAssignableFrom(value.getClass())) { | ||
temp = (Integer)value; |
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.
Why not use pattern matching?
`if (value instanceof Integer intValue) {
temp = intValue;
}
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.
Good question. Given that the earlier changes in the whole set (impl-specific properties) were backported, I assumed this would too, to be complete. Code consistency and clean backport may exceed the benefit of a more advanced code feature (e.g. pattern matching).
I also am still doing works based on JDK 8, that provides a much quicker turnaround.
Saw Patrick's pattern matching changesets for some lib code. It's possible we could do it as well for the xml code. But in general, xml code, esp. those from Apache support a lower source level.
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.
ok, JDK 8 could use instanceof instead of isAssignable.
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. Updated.
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.
Looks fine Joe. Thank you for the additional updates for clarity
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 new table looks fine, ut I think it will be less confusing if the property names are fully qualified (with the jdk.xml prefix) and can be seen as identical to the names in the previous table.
…left instead of center
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.
Look good, Thanks
@JoeWang-Java 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 87 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 |
involve many (57) classes.
…made new ones take preference
/integrate |
@JoeWang-Java Since your change was applied there have been 88 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 8c4719a. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Update module summary, add a few existing properties and features into the tables.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3644/head:pull/3644
$ git checkout pull/3644
Update a local copy of the PR:
$ git checkout pull/3644
$ git pull https://git.openjdk.java.net/jdk pull/3644/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3644
View PR using the GUI difftool:
$ git pr show -t 3644
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3644.diff