-
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
JDK-8289730 : Deprecated code sample in java.lang.ClassCastException #9359
Conversation
How are you dealing with deprecated codes in snippets ? ``` @deprecated(since="9") public Integer(int value) ```
Update Copyright date to 2022.
👋 Welcome back scientificware! A progress list of the required criteria for merging this PR into |
@scientificware 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. |
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.
There is as of yet no systemic way of dealing with compiler warnings with formal or informal snippet samples, but JEP 413: "Code Snippets in Java API Documentation" is meant to enable that.
@jddarcy Thanks. In fact this Issue is related to JEP 413, I had a short informal exchange about this with Jonathan Giles one year ago. It seems that Microsoft already validates snippets in its AzureSDK : https://twitter.com/JonathanGiles/status/1387550356524081154 How JEP 413 process will react with this kind of code ?
In another word, is there a way to specifiy witch result the author expected. JDK-8289775: Update java.lang.invoke.MethodHandle[s] to use snippets |
@scientificware 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 8 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@jddarcy) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@scientificware |
@jddarcy, please could you sponsor this PR ? |
/sponsor |
Going to push as commit 4ad18cf.
Your commit was automatically rebased without conflicts. |
@turbanoff @scientificware Pushed as commit 4ad18cf. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
@turbanoff Thanks. |
This is referenced in Java Bug Database as
This is tracked in JBS as
Description :
Designed from : ScientificWare JDK-8289730 : Deprecated code in src/java.base/share/classes/java/lang/ClassCastException.java
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9359/head:pull/9359
$ git checkout pull/9359
Update a local copy of the PR:
$ git checkout pull/9359
$ git pull https://git.openjdk.org/jdk pull/9359/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9359
View PR using the GUI difftool:
$ git pr show -t 9359
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9359.diff