-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8346232: Remove leftovers of the jar --normalize feature #22751
Conversation
👋 Welcome back eirbjo! A progress list of the required criteria for merging this PR into |
@eirbjo 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 83 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 |
main.help.opt.create.normalize=\ | ||
\ -n, --normalize Normalize information in the new jar archive\n\ | ||
\ after creation. This option is deprecated, and is\n\ | ||
\ planned for removal in a future JDK release |
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.
It does appear to be leftover from when the pack200 and the -n option were removed.
We don't usually touch the translated resources. Oracle updates the translations near the end of each release for the languages supported by Oracle JDK but there are a few translations that are probably out of date now. For removal then it's probably okay.
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.
We don't usually touch the translated resources. [...] For removal then it's probably okay.
What's your recommendation here? Happy to revert changes to translated files, keeping the delete in jar.properties
, if so desirable.
This would rely on Oracle's translation update process catching the remval and update it, ideally in all translations, not only those supported by Oracle JDK, right?
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.
What's your recommendation here? Happy to revert changes to translated files, keeping the delete in
jar.properties
, if so desirable.This would rely on Oracle's translation update process catching the remval and update it, ideally in all translations, not only those supported by Oracle JDK, right?
I think what you have is okay, I'm just saying that we don't usually touch translations when making changes.
Oracle does a refresh the de, ja, and zh_CN translations in each release so I assume the lines you removed will get removed by the next update anyway. @justin-curtis-lu knows more about this "process". I don't know if anyone funds or maintains the other translations now, it's possible that some of these have bit rotted in recent years.
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.
Yes, removing them is fine here. Otherwise we would have caught them during the L10n update anyways.
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.
This looks fine to me.
Thanks for Alan and Jaikiran for reviews and to Justin for the L10n clarification. /integrate |
Going to push as commit 51662c2.
Your commit was automatically rebased without conflicts. |
Please review this cleanup PR which removes a property and a code comment left behind after the
jar --normalize
feature was removed in JDK 14.The feature was deprecated in JDK-8199871 and removed in JDK-8234542, along with removal of Pack200 tools and APIs.
This PR removes the now unused
main.help.opt.create.normalize
property and a code comment inMain.java
referencing normalization.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22751/head:pull/22751
$ git checkout pull/22751
Update a local copy of the PR:
$ git checkout pull/22751
$ git pull https://git.openjdk.org/jdk.git pull/22751/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22751
View PR using the GUI difftool:
$ git pr show -t 22751
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22751.diff
Using Webrev
Link to Webrev Comment