no, that `detekt.gradle.kts` can be in groovy ok s...
# gradle
m
no, that
detekt.gradle.kts
can be in groovy ok so i am fairly confident in at least what the issue is: 1) rootproject has
apply from: 'detekt.gradle.kts'
as the very first thing. i think this will happen after the
buildscript
is evaluated for the buildscript classpath (i would move it underneath) 2) the
kotlin
plugin applies the gradle built-in
java
. when
java
is applied it creates that
convention
above. 3) you aren't applying the
java
or
kotlin
plugin to the rootproject, which looks like it makes sense because you dont have any source in it 4) script compilation fails (with an unhelpful message) because there is no convention or java plugin applied to the root project