-
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
8297794: Deprecate JMX Management Applets for Removal #11430
Conversation
👋 Welcome back kevinw! A progress list of the required criteria for merging this PR into |
@kevinjwalls 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
|
Are you planning to add the @deprecated tag with the description for why they are deprecated? I'm surprised the java.management module compiles without it but maybe this module has doclint config in its make file. |
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 have the same remark as Alan - I believe an @deprecated
text is needed in the API documentation of the public exported classes that are deprecated. At the minimum something like:
* @deprecated This class is deprecated for removal. There is no replacement.
I also see that you have chosen to add @SuppressWarnings
in tests. Not sure what the rules are for the serviceability area - but usually it's fine to keep the deprecation warning in tests (that is: suppressing deprecation warnings in tests is usually optional).
src/java.management/share/classes/javax/management/loading/MLetObjectInputStream.java
Show resolved
Hide resolved
src/java.management/share/classes/javax/management/loading/MLetParser.java
Show resolved
Hide resolved
Thanks both, yes will add a doc comment also. Currently the generated docs give you: "Deprecated, for removal: This API element is subject to removal in a future version." But will add more around that. MLetObjectInputStream and MLetParser are not public classes, so thinking they are not part of the public API we need to deprecate before removal. Happy to try and avoid test logs being full of excess noise with those suppression annotations... 8-) |
Whether a class is public exported or not has no real relationship with whether it should have the |
Updated with additional Deprecated annotations on two non-public classes which would also be removed. |
src/java.management/share/classes/javax/management/loading/MLetParser.java
Outdated
Show resolved
Hide resolved
Added release-note in a subtask for the issue. |
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
@kevinjwalls 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 80 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.
LGTM
Thanks for all the reviews! |
/integrate |
Going to push as commit 17666fb.
Your commit was automatically rebased without conflicts. |
@kevinjwalls Pushed as commit 17666fb. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Deprecate the Java Management Extension (JMX) Management Applet (m-let) feature for removal.
This deprecation will have no impact on users of other JMX features, the JDK's built-in instrumentation, or any of the observability tools.
More details in bug, and CSR JDK-8297795
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11430/head:pull/11430
$ git checkout pull/11430
Update a local copy of the PR:
$ git checkout pull/11430
$ git pull https://git.openjdk.org/jdk pull/11430/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11430
View PR using the GUI difftool:
$ git pr show -t 11430
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11430.diff