Fix deprecations java21 #13223
Merged
Fix deprecations java21 #13223
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the PR. Please consider adding a release note in the help/en/releasenotes/current-draft-note.shtml file. |
|
Merging early for 5.9.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@bobjacobsen
This PR fixes some of the deprecations that will hit us with Java 21. In some cases, I have chosen to suppress the warnings since the replacements isn't available until we move to Java 21. Once we have done the move to Java21, it's easy to fix these.
I have changed the public constructor of
jmri.util.MultipartMessageso that it throws an additional exception. I thought it would be better if the caller handled the originalURISyntaxException, than to have this class throw anIOExceptionwith the URISyntaxException as cause. But it might affect people that are using JMRI as a library.