[Gradle] Use transformDependenciesMetadata task name directly
Using internal TRANSFORM_ALL_SOURCESETS_DEPENDENCIES_METADATA doesn't work well with K2 compiler ^KT-49933
This commit is contained in:
committed by
Space Team
parent
be3e3332d5
commit
1777fc58e7
+1
-4
@@ -345,15 +345,12 @@ class KlibBasedMppIT : BaseGradleIT() {
|
||||
) = with(testCase) {
|
||||
setupWorkingDir()
|
||||
|
||||
@Suppress("INVISIBLE_MEMBER")
|
||||
val transformAllTaskName = KotlinMetadataTargetConfigurator.TRANSFORM_ALL_SOURCESETS_DEPENDENCIES_METADATA
|
||||
|
||||
val printingTaskName = "printItems${testBuildRunId++}"
|
||||
gradleBuildScript(subproject).appendText(
|
||||
"""
|
||||
${'\n'}
|
||||
tasks.register("$printingTaskName") {
|
||||
dependsOn("$transformAllTaskName")
|
||||
dependsOn("transformDependenciesMetadata")
|
||||
doLast {
|
||||
println("###$printingTaskName" + $itemsExpression)
|
||||
}
|
||||
|
||||
+1
-5
@@ -7,7 +7,6 @@ package org.jetbrains.kotlin.gradle
|
||||
|
||||
import org.gradle.api.logging.configuration.WarningMode
|
||||
import org.gradle.util.GradleVersion
|
||||
import org.jetbrains.kotlin.gradle.targets.metadata.KotlinMetadataTargetConfigurator
|
||||
import org.jetbrains.kotlin.gradle.testbase.*
|
||||
import org.junit.jupiter.api.DisplayName
|
||||
import org.junit.jupiter.api.extension.ExtensionContext
|
||||
@@ -660,14 +659,11 @@ class KotlinSpecificDependenciesIT : KGPBaseTest() {
|
||||
if (isBuildGradleKts) buildGradleKts else buildGradle
|
||||
}
|
||||
|
||||
@Suppress("INVISIBLE_MEMBER")
|
||||
val transformAllTaskName = KotlinMetadataTargetConfigurator.TRANSFORM_ALL_SOURCESETS_DEPENDENCIES_METADATA
|
||||
|
||||
buildFile.appendText(
|
||||
"""
|
||||
|
||||
tasks.register("$printingTaskName") {
|
||||
if ("$transformAllTaskName" in tasks.names) dependsOn("$transformAllTaskName")
|
||||
if ("transformDependenciesMetadata" in tasks.names) dependsOn("transformDependenciesMetadata")
|
||||
doLast {
|
||||
println("###$printingTaskName " + $itemsExpression)
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user