-
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
8344252: SM cleanup in java.util classes #22122
Conversation
Remove use of doPrivileged and SecurityManager
👋 Welcome back rriggs! A progress list of the required criteria for merging this PR into |
@RogerRiggs 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 32 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 |
@RogerRiggs 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. |
Webrevs
|
src/java.base/share/classes/java/util/spi/AbstractResourceBundleProvider.java
Outdated
Show resolved
Hide resolved
I mainly wanted to look at Arrays, and I looked briefly at the other stuff too. All looks good. |
* @see <a href="ResourceBundle##resource-bundle-modules"> | ||
* Resource Bundles and Named Modules</a> |
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.
I think HTML tag is not needed:
* @see <a href="ResourceBundle##resource-bundle-modules"> | |
* Resource Bundles and Named Modules</a> | |
* @see ResourceBundle##resource-bundle-modules | |
* Resource Bundles and Named Modules |
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.
LGTM
/integrate |
Going to push as commit c5b6ed8.
Your commit was automatically rebased without conflicts. |
@RogerRiggs Pushed as commit c5b6ed8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
@@ -3722,8 +3654,8 @@ private static String toPackageName(String bundleName) { | |||
|
|||
} | |||
|
|||
private static final boolean TRACE_ON = Boolean.parseBoolean( | |||
GetPropertyAction.privilegedGetProperty("resource.bundle.debug", "false")); | |||
private static final boolean TRACE_ON = Boolean.getBoolean( |
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 update seems to have broken the tracing feature of ResourceBundle.
The previous code called GetPropertyAction::privilegedGetProperty
to get the system property "resource.bundle.debug" with a default of "false". It then used Boolean::parseBoolean
to compare it to "true", ignoring case.
The new code uses System::getProperty
to get the same property, then calls Boolean::getBoolean
which calls System::getProperty
to get the value of the property which name is either "false" or the result of looking up "resource.bundle.debug"
From what I can tell, it is now not possible to enable tracing.
Seems like we could simply use Boolean.getBoolean("resource.bundle.debug")
instead?
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.
Seems like we could simply use
Boolean.getBoolean("resource.bundle.debug")
instead?
Naoto may know the history on this property. It may have been introduced for debugging when working on the RB implementation or maybe it was introduced to allow developers to debug, not sure. If the latter then it's important to preserve long standing behavior. If the former, and it was never documented, there is a lot more flexibility to change.
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.
If the former, and it was never documented, there is a lot more flexibility to change.
Fair enough. However, this SM change seems to accidentally have introduced a bug where the system property is read twice, first calling System.getProperty to look up the name of the system property which is then looked up by Boolean.getBoolean. That behavior just seems broken.
@RogerRiggs may have intended to use Boolean::parseBoolean
instead:
Boolean.parseBoolean(System.getProperty("resource.bundle.debug", "false"))
which is equivalent to:
Boolean.getBoolean("resource.bundle.debug")
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.
Remove use of doPrivileged and SecurityManager in java.util.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22122/head:pull/22122
$ git checkout pull/22122
Update a local copy of the PR:
$ git checkout pull/22122
$ git pull https://git.openjdk.org/jdk.git pull/22122/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22122
View PR using the GUI difftool:
$ git pr show -t 22122
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22122.diff
Using Webrev
Link to Webrev Comment