Update Dokka version references to 2.2.0 (#4485)

(cherry picked from commit b2886ca)

Author: whyoleg

CONTRIBUTING.md

@@ -23,10 +23,10 @@ Bug reports, feature requests and questions are welcome. Submit issues [here](ht
 
 ## Submitting PRs
 
-Dokka has extensive [Developer Guides](https://kotlin.github.io/dokka/2.1.0/developer_guide/introduction/)
+Dokka has extensive [Developer Guides](https://kotlin.github.io/dokka/2.2.0/developer_guide/introduction/)
 documentation
-which goes over the development [Workflow](https://kotlin.github.io/dokka/2.1.0/developer_guide/workflow/) and
-[Dokka's architecture](https://kotlin.github.io/dokka/2.1.0/developer_guide/architecture/architecture_overview/),
+which goes over the development [Workflow](https://kotlin.github.io/dokka/2.2.0/developer_guide/workflow/) and
+[Dokka's architecture](https://kotlin.github.io/dokka/2.2.0/developer_guide/architecture/architecture_overview/),
 which can help you understand how to achieve what you want and where to look.
 
 All development (both new features and bugfixes) takes place in the `master` branch, it contains sources for the next
@@ -64,16 +64,16 @@ not take much time (~2-5 minutes), so please make sure they pass before submitti
 ### Use/test locally built Dokka
 
 Below you will find a bare-bones instruction on how to use and test locally built Dokka. For more details and examples,
-visit [Workflow](https://kotlin.github.io/dokka/2.1.0/developer_guide/workflow/) topic.
+visit [Workflow](https://kotlin.github.io/dokka/2.2.0/developer_guide/workflow/) topic.
 
-1. Publish a custom version of Dokka to Maven Local: `./gradlew publishToMavenLocal -Pversion=2.1.0-my-fix-SNAPSHOT`
+1. Publish a custom version of Dokka to Maven Local: `./gradlew publishToMavenLocal -Pversion=2.2.0-my-fix-SNAPSHOT`
 2. In the project for which you want to generate documentation add Maven Local as a buildscript/dependency
    repository (`mavenLocal()`)
 3. Update your Dokka dependency to the version you've just published:
 
 ```kotlin
 plugins {
-    id("org.jetbrains.dokka") version "2.1.0-my-fix-SNAPSHOT"
+    id("org.jetbrains.dokka") version "2.2.0-my-fix-SNAPSHOT"
 }
 ```
 
@@ -146,7 +146,7 @@ It's possible to run integration tests with a custom Dokka version published to
 via `org.jetbrains.dokka.integration_test.dokkaVersionOverride` Gradle property:
 
 ```bash
-./gradlew :dokka-integration-tests:gradle:testExternalProjectKotlinxCoroutines -Porg.jetbrains.dokka.integration_test.dokkaVersionOverride=2.1.0-dev-329
+./gradlew :dokka-integration-tests:gradle:testExternalProjectKotlinxCoroutines -Porg.jetbrains.dokka.integration_test.dokkaVersionOverride=2.2.0-dev-329
 ```
 
 Additionally, it's possible to open the Gradle integration test projects in IDEA.

README.md

@@ -44,7 +44,7 @@ Apply the Gradle plugin for Dokka in the root build script of your project:
 
 ```kotlin
 plugins {
-    id("org.jetbrains.dokka") version "2.1.0"
+    id("org.jetbrains.dokka") version "2.2.0"
 }
 ```
 
@@ -66,7 +66,7 @@ Apply Gradle plugin for Dokka in the root project:
 
 ```groovy
 plugins {
-    id 'org.jetbrains.dokka' version '2.1.0'
+    id 'org.jetbrains.dokka' version '2.2.0'
 }
 ```
 
@@ -100,7 +100,7 @@ Add the Dokka Maven plugin to the `plugins` section of your POM file:
         <plugin>
             <groupId>org.jetbrains.dokka</groupId>
             <artifactId>dokka-maven-plugin</artifactId>
-            <version>2.1.0</version>
+            <version>2.2.0</version>
             <executions>
                 <execution>
                     <phase>pre-site</phase>
@@ -139,7 +139,7 @@ which aims to improve documentation experience on the Android platform:
 
 ```kotlin
 dependencies {
-    dokkaPlugin("org.jetbrains.dokka:android-documentation-plugin:2.1.0")
+    dokkaPlugin("org.jetbrains.dokka:android-documentation-plugin:2.2.0")
 }
 ```
 
@@ -150,7 +150,7 @@ dependencies {
 
 ```groovy
 dependencies {
-    dokkaPlugin 'org.jetbrains.dokka:android-documentation-plugin:2.1.0'
+    dokkaPlugin 'org.jetbrains.dokka:android-documentation-plugin:2.2.0'
 }
 ```
 
@@ -169,7 +169,7 @@ dependencies {
             <plugin>
                 <groupId>org.jetbrains.dokka</groupId>
                 <artifactId>android-documentation-plugin</artifactId>
-                <version>2.1.0</version>
+                <version>2.2.0</version>
             </plugin>
         </dokkaPlugins>
     </configuration>
@@ -216,7 +216,7 @@ implement plugins for missing or very specific features that are not provided ou
 Learn more about Dokka plugins and their configuration in [Dokka plugins](https://kotlinlang.org/docs/dokka-plugins.html).
 
 If you want to learn how to develop Dokka plugins, see
-[Developer guides](https://kotlin.github.io/dokka/2.1.0/developer_guide/introduction/).
+[Developer guides](https://kotlin.github.io/dokka/2.2.0/developer_guide/introduction/).
 
 Dokka allows you to extend its functionality by [configuring custom plugins](https://github.com/Kotlin/dokka/blob/ae3840edb4e4afd7b3e3768a5fddfe8ec0e08f31/examples/gradle-v2/custom-dokka-plugin-example/demo-library/build.gradle.kts),
 which enable additional processing or modifications to the documentation generation process.

docs-developer/docs/developer_guide/workflow.md

@@ -43,7 +43,7 @@ will review API changes thoroughly, so please make sure it's intentional and rat
 Having built Dokka locally, you can publish it to `mavenLocal()`. This will allow you to test your changes in another
 project as well as debug code remotely.
 
-1. Publish a custom version of Dokka to Maven Local: `./gradlew publishToMavenLocal -Pversion=2.1.0-my-fix-SNAPSHOT`. 
+1. Publish a custom version of Dokka to Maven Local: `./gradlew publishToMavenLocal -Pversion=2.2.0-my-fix-SNAPSHOT`. 
    This version will be propagated to plugins that reside inside Dokka's project (`mathjax`, `kotlin-as-java`, etc),
    and its artifacts should appear in `~/.m2`
 2. In the project you want to generate documentation for or debug on, add maven local as a plugin/dependency
@@ -56,7 +56,7 @@ repositories {
 3. Update your Dokka dependency to the version you've just published:
 ```kotlin
 plugins {
-    id("org.jetbrains.dokka") version "2.1.0-my-fix-SNAPSHOT"
+    id("org.jetbrains.dokka") version "2.2.0-my-fix-SNAPSHOT"
 }
 ```
 

docs/topics/dokka-gradle-configuration-options.md

@@ -349,7 +349,7 @@ dokka {
         </p>
         <p>
             Additionally, you can use Dokka's 
-            <a href="https://github.com/Kotlin/dokka/blob/v2.1.0/dokka-runners/dokka-gradle-plugin/src/main/kotlin/engine/parameters/HasConfigurableVisibilityModifiers.kt"><code>documentedVisibilities()</code> function</a> 
+            <a href="https://github.com/Kotlin/dokka/blob/v2.2.0/dokka-runners/dokka-gradle-plugin/src/main/kotlin/engine/parameters/HasConfigurableVisibilityModifiers.kt"><code>documentedVisibilities()</code> function</a> 
             to add documented visibilities.
         </p>
         <p>This can be configured for each individual package.</p>

docs/topics/dokka-migration.md

@@ -233,7 +233,7 @@ documentedVisibilities.set(
 documentedVisibilities(VisibilityModifier.Public)
 ```
 
-Additionally, use DGP v2's [utility function](https://github.com/Kotlin/dokka/blob/v2.1.0/dokka-runners/dokka-gradle-plugin/src/main/kotlin/engine/parameters/HasConfigurableVisibilityModifiers.kt#L14-L16) to add documented visibilities:
+Additionally, use DGP v2's [utility function](https://github.com/Kotlin/dokka/blob/v2.2.0/dokka-runners/dokka-gradle-plugin/src/main/kotlin/engine/parameters/HasConfigurableVisibilityModifiers.kt#L14-L16) to add documented visibilities:
 
 ```kotlin
 fun documentedVisibilities(vararg visibilities: VisibilityModifier): Unit =

docs/topics/dokka-plugins.md

@@ -148,7 +148,7 @@ For an example of Dokka plugins configuration, see the
 
 Dokka allows you 
 to extend its functionality
-and modify the documentation generation process by [configuring custom plugins](https://github.com/Kotlin/dokka/blob/v2.1.0/examples/gradle-v2/custom-dokka-plugin-example/demo-library/build.gradle.kts).
+and modify the documentation generation process by [configuring custom plugins](https://github.com/Kotlin/dokka/blob/v2.2.0/examples/gradle-v2/custom-dokka-plugin-example/demo-library/build.gradle.kts).
 
 </tab>
 <tab title="Gradle Groovy DSL" group-key="groovy">

docs/v.list

@@ -4,9 +4,9 @@
 
 <vars>
     <var name="dokkaVersion"
-         value="2.1.0"
+         value="2.2.0"
          type="string"/>
     <var name="kotlinVersion"
-         value="2.1.0"
+         value="2.3.0"
          type="string"/>
 </vars>

dokka-integration-tests/gradle/projects/README.md

@@ -3,8 +3,8 @@
 Projects used to run integration tests could be opened in or build independently by following these steps:
 
 1. open `gradle.properties` file of a specific project and change commented variables:
-    1. `dokka_it_kotlin_version` to required version of Kotlin Gradle Plugin, e.g 2.1.0
-    2. `dokka_it_dokka_version` to required version to Dokka Gradle plugin, e.g 2.1.0
+    1. `dokka_it_kotlin_version` to required version of Kotlin Gradle Plugin, e.g 2.3.0
+    2. `dokka_it_dokka_version` to required version to Dokka Gradle plugin, e.g 2.2.0
     3. replace all other commented properties if needed, like `dokka_it_android_gradle_plugin_version`
 2. open `settings.gradle.kts` and replace `apply(from = "template.settings.gradle.kts")` with
    `apply(from = "../template.settings.gradle.kts")` (so the path should be prefixed with `../`)

dokka-subprojects/analysis-kotlin-symbols/README.md

@@ -24,7 +24,7 @@ To build it with an override version of Analysis API, the property
 
 ### Entry point
 
-The main entry point is `DefaultSymbolToDocumentableTranslator` (this is an extension for [the extension point](https://kotlin.github.io/dokka/2.1.0/developer_guide/architecture/extension_points/core_extensions/#sourcetodocumentabletranslator) ), that is used by the Dokka core to build Documentable model by a source set.
+The main entry point is `DefaultSymbolToDocumentableTranslator` (this is an extension for [the extension point](https://kotlin.github.io/dokka/2.2.0/developer_guide/architecture/extension_points/core_extensions/#sourcetodocumentabletranslator) ), that is used by the Dokka core to build Documentable model by a source set.
 
 Across running Dokka we keep `StandaloneAnalysisAPISession` and `KtSourceModule` instances from Analysis API into `KotlinAnalysis`.
 `KotlinAnalysis` is used in `DefaultSymbolToDocumentableTranslator` and other services that need an additional analysis.
@@ -51,4 +51,4 @@ By default, we run unit tests on TeamCity against the latest Analysis API by a s
 - You can use the `gradle :publishToMavenLocal` task to publish Dokka locally.
 - To build Dokka without running testing, using the `gradle assemble` task is recommended since the tests are time-consuming.
 
-See the detailed guide [here](https://kotlin.github.io/dokka/2.1.0/developer_guide/workflow/).
+See the detailed guide [here](https://kotlin.github.io/dokka/2.2.0/developer_guide/workflow/).

dokka-subprojects/plugin-kotlin-as-java/README.md

@@ -8,7 +8,7 @@ The Kotlin as Java plugin is published to maven central as a
 [separate artifact](https://mvnrepository.com/artifact/org.jetbrains.dokka/kotlin-as-java-plugin):
 
 ```text
-org.jetbrains.dokka:kotlin-as-java-plugin:2.1.0
+org.jetbrains.dokka:kotlin-as-java-plugin:2.2.0
 ```
 
 **This plugin is at its early stages**, so you may experience issues and encounter bugs. Feel free to