-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8308046: Move Solaris related charsets from java.base to jdk.charsets module #13973
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
…e to jdk.charsets module
👋 Welcome back itakiguchi! A progress list of the required criteria for merging this PR into |
/label remove build |
@takiguc |
Webrevs
|
/label add core-libs |
@naotoj |
I now think it is better simply removing Solaris-related charsets, as moving them from java.base to jdk.charsets would require unnecessary code changes in non-Solaris code. |
Hello @naotoj . |
OK, maybe not now. I think the fix may be simplified by changing access for those Also, please drop |
private static final SingleByte.Decoder DEC0201 = | ||
(SingleByte.Decoder)new JIS_X_0201().newDecoder(); | ||
|
||
private static final DoubleByte.Decoder DEC0208 = | ||
(DoubleByte.Decoder)new JIS_X_0208().newDecoder(); | ||
|
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.
Can these also be removed, by making those original ones in EUC_JP
public?
Scratch that, you've already did it. Then you can remove these:
|
Hello @naotoj . |
I meant making those package-private fields public. I believe it's OK because java.base/sun.nio.cs package is only exported to jdk.charsets module. |
Thanks @naotoj . |
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 good. I think you may want to change stdcs-aix
as well.
As to the JBS issue, please change the title to match the PR title, and add noreg-cleanup
label
Hello @naotoj . |
@takiguc 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 116 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 |
/integrate |
Going to push as commit 5d8ba93.
Your commit was automatically rebased without conflicts. |
According to "JDK 20 Internationalization Guide"
https://docs.oracle.com/en/java/javase/20/intl/supported-encodings.html
Following Solaris related charsets are in "contained in jdk.charsets module" list.
These are not supported by Linux platform, so they should not be in java.base module.
Note:
GHA Linux x86 builds were failed.
I think it's not related by my modified code.
I opened JDK-8308051 GHA: Linux x86 builds failure
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/13973/head:pull/13973
$ git checkout pull/13973
Update a local copy of the PR:
$ git checkout pull/13973
$ git pull https://git.openjdk.org/jdk.git pull/13973/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 13973
View PR using the GUI difftool:
$ git pr show -t 13973
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13973.diff
Webrev
Link to Webrev Comment