DatatypeConverter replaced with Base64 decoder #158
Merged
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
The DatatypeConverter was part of the javax.xml.bind and therefore needs to be replaced with Base64 decoder from the java util packages to smooth transition to Java9.
hoegertn
approved these changes
Feb 11, 2019
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.
The DatatypeConverter was part of the javax.xml.bind and therefore needs
to be replaced with Base64 decoder from the java util packages to smooth
transition to Java9.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Is one part of removing javax.xml.bind classes to smooth transition to java 9 where this package is removed.
What is the current behavior? (You can also link to an open issue here)
https://issues.jenkins-ci.org/browse/JENKINS-55954
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their setup due to this PR?)
No change required.
Other information: