Fix Utils.toIsoDateFormat() for non-English locales. #116
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
|
Thank you for this @kaitoy! |
|
I've signed it. |
|
@kaitoy, release 1.7 includes your fix. Thanks. |
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.
When a user set bintray.pkg.version.released to a Date instance, its string representation will be passed to toIsoDateFormat() and parsed by the dateToStringFormat.
But in non-English locales such as Japanese, this parse fails because a Date instance is always converted to an English string but a SimpleDateFormat object instantiated without specifying a locale attempts to parse a given string in the JVM locale (i.e. non-English), which results in an error like "java.text.ParseException: Unparseable date: "Fri Apr 29 10:03:11 MDT 2016"".
To avoid this error, Locale.English is added to SimpleDateFormat's constructor.