diff --git a/docs/kr.tree b/docs/kr.tree index 68a35503f09..bb7467e9499 100644 --- a/docs/kr.tree +++ b/docs/kr.tree @@ -148,7 +148,7 @@ - + diff --git a/docs/topics/gradle/gradle-compilation-and-caches.md b/docs/topics/gradle/gradle-compilation-and-caches.md index d1f43b43c9e..48241b1a64b 100644 --- a/docs/topics/gradle/gradle-compilation-and-caches.md +++ b/docs/topics/gradle/gradle-compilation-and-caches.md @@ -221,7 +221,7 @@ There are three compiler execution strategies: | Strategy | Where Kotlin compiler is executed | Incremental compilation | Other characteristics and notes | |----------------|--------------------------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Daemon | Inside its own daemon process | Yes | *The default and fastest strategy*. Can be shared between different Gradle daemons and multiple parallel compilations. | +| Daemon | Inside its own daemon process | Yes | _The default and fastest strategy_. Can be shared between different Gradle daemons and multiple parallel compilations. | | In process | Inside the Gradle daemon process | No | May share the heap with the Gradle daemon. The "In process" execution strategy is _slower_ than the "Daemon" execution strategy. Each [worker](https://docs.gradle.org/current/userguide/worker_api.html) creates a separate Kotlin compiler classloader for each compilation. | | Out of process | In a separate process for each compilation | No | The slowest execution strategy. Similar to the "In process", but additionally creates a separate Java process within a Gradle worker for each compilation. | @@ -355,7 +355,7 @@ There are two common cases that analyzing build reports for long-running compila save separate classes in different files, refactor large classes, declare top-level functions in different files, and so on. Learn [how to read build reports](https://blog.jetbrains.com/kotlin/2022/06/introducing-kotlin-build-reports/#how_to_read_build_reports) -and [how build JetBrains uses build reports](https://blog.jetbrains.com/kotlin/2022/06/introducing-kotlin-build-reports/#how_we_use_build_reports_in_jetbrains). +and [how JetBrains uses build reports](https://blog.jetbrains.com/kotlin/2022/06/introducing-kotlin-build-reports/#how_we_use_build_reports_in_jetbrains). ### Enabling build reports @@ -401,12 +401,13 @@ kotlin.build.report.label=some_label ### Limit of custom values To collect build scans' statistics, Kotlin build reports use [Gradle's custom values](https://docs.gradle.com/enterprise/tutorials/extending-build-scans/). -Different Gradle plugins and you can also write data to custom values. The number of custom values has a limit. -See the current maximum custom value count in the [Build scan plugin docs](https://docs.gradle.com/enterprise/gradle-plugin/#adding_custom_values). +Both you and different Gradle plugins can write data to custom values. The number of custom values has a limit. +See the current maximum custom value count in the [Build scan plugin docs](https://docs.gradle.com/enterprise/gradle-plugin/#adding_custom_values). + If you have a big project, a number of such custom values may be quite big. If this number exceeds the limit, you can see the following message in the logs: -``` +```text Maximum number of custom values (1,000) exceeded ``` @@ -420,8 +421,10 @@ kotlin.build.report.build_scan.custom_values_limit=500 HTTP build statistic logs can contain some project and system properties. These properties can change builds' behavior, so it's useful to log them in build statistics. -These properties can store sensitive data, for example, passwords or a project's full path. -You can turn on this behavior by adding the `kotlin.build.report.http.verbose_environment` property to your `gradle.properties`. +These properties can store sensitive data, for example, passwords or a project's full path. + +You can disable collection of these statistics by adding the `kotlin.build.report.http.verbose_environment` property to +your `gradle.properties`. > JetBrains doesn't collect these statistics. You choose a place [where to store your reports](#enabling-build-reports). > diff --git a/docs/topics/multiplatform-mobile/multiplatform-mobile-samples.md b/docs/topics/multiplatform-mobile/multiplatform-mobile-samples.md index e67535a3bc9..22682e021e7 100644 --- a/docs/topics/multiplatform-mobile/multiplatform-mobile-samples.md +++ b/docs/topics/multiplatform-mobile/multiplatform-mobile-samples.md @@ -124,6 +124,7 @@ This is a curated list of Kotlin Multiplatform Mobile samples. - ✅ +

Target list:

  • Android Wear OS
  • iOS
    • diff --git a/docs/topics/multiplatform/multiplatform-native-artifacts.md b/docs/topics/multiplatform/multiplatform-native-artifacts.md index beaf946f486..30dceddad2d 100644 --- a/docs/topics/multiplatform/multiplatform-native-artifacts.md +++ b/docs/topics/multiplatform/multiplatform-native-artifacts.md @@ -1,4 +1,4 @@ -[//]: # (title: Build Kotlin/Native artifacts) +[//]: # (title: Build final native binaries (Experimental DSL)) > The new DSL described below is [Experimental](components-stability.md). It may be changed at any time. > We encourage you to use it for evaluation purposes. diff --git a/docs/topics/whatsnew18.md b/docs/topics/whatsnew18.md index 74d2b0d35cb..60b07d0734e 100644 --- a/docs/topics/whatsnew18.md +++ b/docs/topics/whatsnew18.md @@ -15,9 +15,9 @@ The Kotlin 1.8.0 release is out and here are some of its biggest highlights: The Kotlin plugin that supports 1.8.0 is available for: -| IDE | Supported versions | -|---------------|------------------------------------| -| IntelliJ IDEA | 2021.3, 2022.1, 2022.2 | +| IDE | Supported versions | +|----------------|------------------------------------| +| IntelliJ IDEA | 2021.3, 2022.1, 2022.2 | | Android Studio | Electric Eel (221), Flamingo (222) | > You can update your projects to Kotlin 1.8.0 in IntelliJ IDEA 2022.3 without updating the IDE plugin. @@ -127,7 +127,7 @@ To make Kotlin more interoperable with Objective-C and Swift, three new annotati replacing a Kotlin declaration with a wrapper written in Swift. The annotation instructs the Kotlin compiler to mark a function or property as `swift_private` in the generated - Objective-C API. Such declarations get the `**` prefix, which makes them invisible to Swift code. + Objective-C API. Such declarations get the `__` prefix, which makes them invisible to Swift code. You can still use these declarations in your Swift code to create a Swift-friendly API, but they won't be suggested by Xcode's autocompletion, for example. @@ -184,17 +184,17 @@ Here are some of the key differences between the two layouts: #### KotlinSourceSet naming schema -| Current source set layout | New source set layout | -|----------------------------------------|---------------------------------| -| `targetName` + `AndroidSourceSet.name` | targetName + AndroidVariantType | +| Current source set layout | New source set layout | +|----------------------------------------|-------------------------------------| +| `targetName` + `AndroidSourceSet.name` | `targetName` + `AndroidVariantType` | `{AndroidSourceSet.name}` maps to `{KotlinSourceSet.name}` as follows: -| `AndroidSourceSet.name` | `KotlinSourceSet.name` in current source set layout | `KotlinSourceSet.name` in new source set layout | -|-------------------------|-----------------------------------------------------|-------------------------------------------------| -| main | androidMain | androidMain | -| test | androidTest | androidUnitTest | -| androidTest | androidAndroidTest | androidInstrumentedTest | +| | Current source set layout | New source set layout | +|-------------|---------------------------|--------------------------------| +| main | androidMain | androidMain | +| test | androidTest | androidUnitTest | +| androidTest | androidAndroidTest | androidInstrumentedTest | #### SourceDirectories @@ -202,26 +202,26 @@ Here are some of the key differences between the two layouts: |---------------------------------------------------------|---------------------------------------------------------------------------| | The layout adds additional `/kotlin` SourceDirectories | `src/{AndroidSourceSet.name}/kotlin`, `src/{KotlinSourceSet.name}/kotlin` | -`{AndroidSourceSet.name}` maps to `{Source Directories included}` as follows: +`{AndroidSourceSet.name}` maps to `{SourceDirectories included}` as follows: -| `AndroidSourceSet.name` | `{Source Directories included}` in current source set layout | `{Source Directories included}` in new source set layout | -|-------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| -| main | src/androidMain/kotlin, src/main/kotlin, src/main/java | src/androidMain/kotlin, src/main/kotlin, src/main/java | -| test | src/androidTest/kotlin, src/test/kotlin, src/test/java | src/androidUnitTest/kotlin, src/test/kotlin, src/test/java | -| androidTest | src/androidAndroidTest/kotlin, src/androidTest/java | src/androidInstrumentedTest/kotlin, src/androidTest/java, src/androidTest/kotlin | +| | Current source set layout | New source set layout | +|-------------|------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| main | src/androidMain/kotlin, src/main/kotlin, src/main/java | src/androidMain/kotlin, src/main/kotlin, src/main/java | +| test | src/androidTest/kotlin, src/test/kotlin, src/test/java | src/androidUnitTest/kotlin, src/test/kotlin, src/test/java | +| androidTest | src/androidAndroidTest/kotlin, src/androidTest/java | src/androidInstrumentedTest/kotlin, src/androidTest/java, src/androidTest/kotlin | #### The location of the `AndroidManifest.xml` file | Current source set layout | New source set layout | |--------------------------------------------------------|-------------------------------------------------------| -| src/{AndroidSourceSet.name}/AndroidManifest.xml | src/{KotlinSourceSet.name}/AndroidManifest.xml | +| src/{AndroidSourceSet.name}/AndroidManifest.xml | src/{KotlinSourceSet.name}/AndroidManifest.xml | `{AndroidSourceSet.name}` maps to`{AndroidManifest.xml location}` as follows: -| `AndroidSourceSet.name` | `{AndroidManifest.xml location}` in current source set layout | `{AndroidManifest.xml location}` in new source set layout | -|-------------------------|---------------------------------------------------------------|-----------------------------------------------------------| -| main | src/main/AndroidManifest.xml | src/androidMain/AndroidManifest.xml | -| debug | src/debug/AndroidManifest.xml | src/androidDebug/AndroidManifest.xml | +| | Current source set layout | New source set layout | +|-------|-------------------------------|---------------------------------------------| +| main | src/main/AndroidManifest.xml | src/androidMain/AndroidManifest.xml | +| debug | src/debug/AndroidManifest.xml | src/androidDebug/AndroidManifest.xml | ### Configuration and setup @@ -231,7 +231,7 @@ The new layout will become the default in future releases. You can enable it now kotlin.mpp.androidSourceSetLayoutVersion=2 ``` -> The new layout requires Android Gradle plugin 7.0 or later and is supported in Android Studio > 2022.3 and later. +> The new layout requires Android Gradle plugin 7.0 or later and is supported in Android Studio 2022.3 and later. > {type="note"}