Even though we use project.build.sourceEncoding, on Windows, you still seem to
have to specify file encoding explicitly using JAVA_TOOL_OPTIONS
i.e.:
[Environment]::SetEnvironmentVariable("JAVA_TOOLS_OPTIONS",
"-Dfile.encoding=UTF8", "Machine")
otherwise the new test fails. Leads me to think we
Closed #1083.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1083#event-1028296800
Squashed, reworded commit message, and pushed to master as
d41101df5932043c3a8614552f25ab91194595ba. I encountered conflicts when
cherry-picking to 2.0.x so please submit another pull request if you want to
backport this. Thank you for your contribution @matmannion!
--
You are receiving this
@andrewgaul I've added a live integration test for this change
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1083#issuecomment-291444626
@matmannion pushed 1 commit.
a59c3b4 JCLOUDS-1264: Add live integration test for unicode container names
and object names through the StaticLargeObjectApi
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/jclouds/jclouds/pull/1083/files
Ditto about integration tests, this time in `StaticLargeObjectApiLiveTest`.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1083#issuecomment-291394650
This fixes a bug where previously BindManifestToJsonPayload used the character
length as the ContentLength, instead of the byte length, which caused issues if
the JSON contained multi-byte Unicode characters.
You can view, comment on, or merge this pull request online at:
https://github.com/jc
