From 5eeb2bbeb8c71ae813808ee0e8d09293c4abe1c1 Mon Sep 17 00:00:00 2001
From: Ignat Beresnev <ignat.beresnev@jetbrains.com>
Date: Thu, 19 Jan 2023 04:10:57 +0100
Subject: Revise README documentation for examples and plugins (#2736)

---
 .../parentProject/build.gradle.kts                 | 35 +++++++++++++++-------
 1 file changed, 24 insertions(+), 11 deletions(-)

(limited to 'examples/gradle/dokka-multimodule-example/parentProject/build.gradle.kts')

diff --git a/examples/gradle/dokka-multimodule-example/parentProject/build.gradle.kts b/examples/gradle/dokka-multimodule-example/parentProject/build.gradle.kts
index 397ad22f..66b32b18 100644
--- a/examples/gradle/dokka-multimodule-example/parentProject/build.gradle.kts
+++ b/examples/gradle/dokka-multimodule-example/parentProject/build.gradle.kts
@@ -1,19 +1,32 @@
+import org.jetbrains.dokka.DokkaConfiguration.Visibility
+import org.jetbrains.dokka.gradle.DokkaTaskPartial
+
 plugins {
-    /**
-     * Kotlin plugin necessary because of potential Gradle bug!
-     * This is not necessary if the kotlin gradle plugin is added as buildscript
-     * dependency like
-     *
-     * buildscript {
-     *     dependencies {
-     *         classpath("org.jetbrains.kotlin:kotlin-gradle-plugin")
-     *     }
-     * }
-     */
     kotlin("jvm")
     id("org.jetbrains.dokka")
 }
 
+// You can apply and configure Dokka in each subproject
+// individially or configure all subprojects at once
+subprojects {
+    apply(plugin = "org.jetbrains.dokka")
+
+    tasks.withType<DokkaTaskPartial>().configureEach {
+        dokkaSourceSets.configureEach {
+            documentedVisibilities.set(setOf(
+                Visibility.PUBLIC,
+                Visibility.PROTECTED
+            ))
+        }
+    }
+}
+
+// Configures only the parent MultiModule task,
+// this will not affect subprojects
+tasks.dokkaHtmlMultiModule {
+    moduleName.set("Dokka MultiModule Example")
+}
+
 dependencies {
     implementation(kotlin("stdlib"))
 }
-- 
cgit