Workaround instability of Gradle builds caused by the default encoding

The encoding setting from org.gradle.jvmargs is not applied
(https://github.com/gradle/gradle/issues/22292) during
the :kotlin-stdlib-js:compileJs, causing instability in kotlin.js.map
(https://youtrack.jetbrains.com/issue/KT-50589) on machines where
default encoding is not UTF-8.

This reverts commit d7ef5efa6a.

KTI-932
This commit is contained in:
Nikolay Krasko
2022-10-03 10:30:50 +02:00
committed by Space Team
parent 289f540530
commit b5b58f40d6
2 changed files with 3 additions and 1 deletions
+2
View File
@@ -1,5 +1,7 @@
org.gradle.jvmargs=-Duser.country=US -Dfile.encoding=UTF-8 -Dorg.gradle.internal.publish.checksums.insecure=true
kotlin.daemon.jvmargs=-Xmx3g
systemProp.file.encoding=UTF-8
systemProp.user.country=US
# Enable new incremental compiation
kotlin.incremental.useClasspathSnapshot=true
+1 -1
View File
@@ -71,7 +71,7 @@ public actual fun Char.uppercaseChar(): Char {
*
* This function supports one-to-many character mapping, thus the length of the returned string can be greater than one.
* For example, `'\uFB00'.uppercase()` returns `"\u0046\u0046"`,
* where `'\uFB00'` is the LATIN SMALL LIGATURE FF character.
* where `'\uFB00'` is the LATIN SMALL LIGATURE FF character (`ff`).
* If this character has no upper case mapping, the result of `toString()` of this char is returned.
*
* @sample samples.text.Chars.uppercase