Fixing call to JDK7+ method to maintain JDK6 Runtime compatibility#530
Merged
Fixing call to JDK7+ method to maintain JDK6 Runtime compatibility#530
Conversation
|
👍 be100a0 |
alexmoore
added a commit
that referenced
this pull request
Jul 27, 2015
Fixing call to JDK7+ method to maintain JDK6 Runtime compatibility
Contributor
|
Related to this, are there plans to make 1.7 the default since 1.6 was end of life on Feb. 2013. JDK7 was end of life on April 2015 but I realize most enterprises are still using JDK7 at this point. Removing JDK6 would at least encourage people to start moving toward something more recent. |
Contributor
Author
|
I know :( I'll have to double check that there aren't any customers still on 1.6, I'd love to advance it as well. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fix for #527 (CLIENTS-521).
getHostString()forgetHostName(), which should be in JRE6.java.net.StandardSocketOptionswas introduced in JDK7, and remains as it's within a test and shouldn't be a runtime issue.