Support applying the plugin to any project in hierarchy (Kotlin#39)

This change removes accesses to the extension via `rootProject`. Instead, we now access the extension wherever it was actually created. This means that when applying the plugin to a project that is not the rootProject, we will use the correct extension instead of looking for it in the rootProject (where it is not). Fixes Kotlin#37
balao7 · Feb 1, 2021 · 29267dd · 29267dd
1 parent 3ed63f9
commit 29267dd
Show file tree

Hide file tree

Showing 5 changed files with 347 additions and 179 deletions.
diff --git a/src/functionalTest/kotlin/kotlinx/validation/test/IgnoredClassesTest.kt b/src/functionalTest/kotlin/kotlinx/validation/test/IgnoredClassesTest.kt
diff --git a/...tlinx/validation/test/SubprojectsTests.kt → .../test/SubprojectsWithPluginOnRootTests.kt b/...tlinx/validation/test/SubprojectsTests.kt → .../test/SubprojectsWithPluginOnRootTests.kt
@@ -16,7 +16,7 @@ import org.assertj.core.api.Assertions
 import org.junit.Test
 import kotlin.test.assertTrue
 
-internal class SubprojectsTests : BaseKotlinGradleTest() {
+internal class SubprojectsWithPluginOnRootTests : BaseKotlinGradleTest() {
 
     /**
      * Sets up a project hierarchy like this: