From ee0f55d8e113a2bd5e5b4b43a64f9b5a51c41cf6 Mon Sep 17 00:00:00 2001 From: Ilya Chernikov Date: Tue, 16 Jul 2019 15:56:59 +0200 Subject: [PATCH] Fix gradle IT with scripting discovery The test is not designed to fail if the definitions are not discovered - the script files have completely custom extensions and therefore ignored. So checking for the warning in the build log is enough. #KT-32697 fixed --- .../src/test/kotlin/org/jetbrains/kotlin/gradle/SubpluginsIT.kt | 1 - 1 file changed, 1 deletion(-) diff --git a/libraries/tools/kotlin-gradle-plugin-integration-tests/src/test/kotlin/org/jetbrains/kotlin/gradle/SubpluginsIT.kt b/libraries/tools/kotlin-gradle-plugin-integration-tests/src/test/kotlin/org/jetbrains/kotlin/gradle/SubpluginsIT.kt index db862d3a839..38eccfa2092 100644 --- a/libraries/tools/kotlin-gradle-plugin-integration-tests/src/test/kotlin/org/jetbrains/kotlin/gradle/SubpluginsIT.kt +++ b/libraries/tools/kotlin-gradle-plugin-integration-tests/src/test/kotlin/org/jetbrains/kotlin/gradle/SubpluginsIT.kt @@ -160,7 +160,6 @@ class SubpluginsIT : BaseGradleIT() { assertCompiledKotlinSources(project.relativize(bobGreet, aliceGreet, worldGreet, greetScriptTemplateKt)) } } else { - assertFailed() val usedGradleVersion = GradleVersion.version( System.getProperty("kotlin.gradle.version.for.tests")