azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix pill problem with main-kts-test, reenabling pill for main-kts modules

Browse Source
This commit is contained in:
Ilya Chernikov
2018-09-27 16:03:46 +02:00
parent 0303fc036c
commit 499146db0e
2 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
libraries/tools/kotlin-main-kts-test/build.gradle.kts
+2 -1
View File
@@ -3,13 +3,14 @@ description = "Kotlin \"main\" script definition tests"
plugins { plugins {
kotlin("jvm") kotlin("jvm")
id("jps-compatible")
} }
dependencies { dependencies {
testCompile(project(":kotlin-main-kts")) testCompile(project(":kotlin-main-kts"))
testCompile(project(":kotlin-scripting-jvm-host")) testCompile(project(":kotlin-scripting-jvm-host"))
testCompile(commonDep("junit")) testCompile(commonDep("junit"))
testRuntime("org.apache.ivy:ivy:2.4.0") compileOnly("org.apache.ivy:ivy:2.4.0") // for jps/pill
} }
sourceSets { sourceSets {
libraries/tools/kotlin-main-kts/build.gradle.kts
+1
View File
@@ -6,6 +6,7 @@ description = "Kotlin \"main\" script definition"
plugins { plugins {
kotlin("jvm") kotlin("jvm")
id("jps-compatible")
} }
// You can run Gradle with "-Pkotlin.build.proguard=true" to enable ProGuard run on the jar (on TeamCity, ProGuard always runs) // You can run Gradle with "-Pkotlin.build.proguard=true" to enable ProGuard run on the jar (on TeamCity, ProGuard always runs)