From 63856cff1bb145cc1fda8a8ee9b8e87bf4fbb5c6 Mon Sep 17 00:00:00 2001 From: Mikhail Glukhikh Date: Tue, 6 Nov 2018 13:46:09 +0300 Subject: [PATCH] Fix failing GradleImportingTestCase-based tests in 183 #KT-28026 Fixed To fix this, we say explicitly not to use qualified module names option during Gradle import Related to IDEA-201249 --- .../kotlin/idea/codeInsight/gradle/GradleImportingTestCase.kt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/idea/idea-gradle/tests/org/jetbrains/kotlin/idea/codeInsight/gradle/GradleImportingTestCase.kt b/idea/idea-gradle/tests/org/jetbrains/kotlin/idea/codeInsight/gradle/GradleImportingTestCase.kt index cd912e1919c..e3cad2d92a6 100644 --- a/idea/idea-gradle/tests/org/jetbrains/kotlin/idea/codeInsight/gradle/GradleImportingTestCase.kt +++ b/idea/idea-gradle/tests/org/jetbrains/kotlin/idea/codeInsight/gradle/GradleImportingTestCase.kt @@ -95,7 +95,9 @@ abstract class GradleImportingTestCase : ExternalSystemImportingTestCase() { FileTypeManager.getInstance().associateExtension(GroovyFileType.GROOVY_FILE_TYPE, "gradle") } - myProjectSettings = GradleProjectSettings() + myProjectSettings = GradleProjectSettings().apply { + this.isUseQualifiedModuleNames = false + } GradleSettings.getInstance(myProject).gradleVmOptions = "-Xmx128m -XX:MaxPermSize=64m" System.setProperty(ExternalSystemExecutionSettings.REMOTE_PROCESS_IDLE_TTL_IN_MS_KEY, GRADLE_DAEMON_TTL_MS.toString()) configureWrapper()