spierce7
05/28/2017, 4:16 PMconfigurations {
provided
}
sourceSets {
main {
compileClasspath += configurations.provided
runtimeClasspath += configurations.provided
}
test {
compileClasspath += configurations.provided
runtimeClasspath += configurations.provided
}
customSourceSet
}
dependencies {
provided project(':Core')
}
I'm assuming I'd need to think of it differently with gradle-kotlin-script
? Maybe I'd be using something extension functions to add similar behavior?
I'm also not sure how I'd do something like customSourceSetCompile
in kotlin-script-gradle
, and am curious what the solution is.suresh
05/29/2017, 2:44 PMfun Project.sourceSets(block: SourceSetContainer.() -> Unit) = the<JavaPluginConvention>().sourceSets.apply(block)
val SourceSetContainer.main: SourceSet get() = this["main"]
val SourceSetContainer.test: SourceSet get() = this["test"]
fun SourceSetContainer.main(block: SourceSet.() -> Unit) = main.apply(block)
fun SourceSetContainer.test(block: SourceSet.() -> Unit) = test.apply(block)
sourceSets {
main {
println("${name.capitalize()} => Java : ${java.srcDirs}, Kotlin: ${kotlin.srcDirs}, Resource: ${resources.srcDirs}")
}
test {
println("${name.capitalize()} => Java : ${java.srcDirs}, Kotlin: ${kotlin.srcDirs}, Resource: ${resources.srcDirs}")
}
}
val SourceSet.kotlin: SourceDirectorySet get() = (this as HasConvention).convention.getPlugin<KotlinSourceSet>().kotlin
spierce7
05/29/2017, 2:51 PM