A modern programming language that makes developers happier.

kotlinlang

I’m getting a huge number of compilation errors when I run `./gradlew detektMain` on my Android project. Including this… :joy:
```error: 'trySend(E): ChannelResult&lt;Unit&gt;' is only available since Kotlin 1.4.30 and cannot be used in Kotlin 1.5```
These errors don’t come up when compiling normally, what’s happening here?

1.15.0 at the moment. I tried to use 1.18.0 but it complained about my config file being invalid at “comments&gt;excludes” so I backtracked

I have these applied to my subprojects
```tasks.withType&lt;Detekt&gt; {
    jvmTarget = "11"
}```
```detekt {
    toolVersion = Dependencies.Libraries.detektVersion
    input = files("src/main/java")
    config = rootProject.files("buildSrc/detekt.yml")
}```


You would need to update to `1.18.0` to make it work correctly. The reason is that `1.15.x` was using a older version of Kotlin: <https://detekt.github.io/detekt/compatibility.html#detekt-support-commitment>
Therefore it’s loading a older version of kotlin-compiler-embeddable and is not able to analyse your code correctly.

We will do a point release soon-ish to fix the issue you’re experiencing with `"comments&gt;excludes"`

So if I understand correctly, the Kotlin version being used is determined by Detekt, not the project it’s in?

In the future we’re looking into offering this: <http://github.com/detekt/detekt-compiler-plugin/|github.com/detekt/detekt-compiler-plugin/>

This will make integration with your normal compilation flow easier.

Awesome, I’ll wait for the 1.18.1 release then - is there a timeline?

I’ve upgraded to 1.18.0 but I’m still getting compilation errors, e.g.
```error: class 'MyClass' is not abstract and does not implement abstract member public abstract fun describeContents(): Int defined in android.os.Parcelable```
for a class that has `@Parcelize`
and lots of `error: unresolved reference: someVar`

That’s potentially the same issue as: <https://github.com/detekt/detekt/issues/3272>

Yep it sounds a lot like what it quotes in there:
&gt; This is due to the inability to gather the complete compile classpath from the Android Gradle Plugin (upstream ticket) and can safely be ignored.
I’ll just wait for the Kotlin compiler plugin and ignore the errors for now

Yes so you’ll probably see those compilation error, but Detekt will run regardless (with some unresolved symbols).

It might be nice to have that on the documentation somewhere, since it really looks like something’s gone wrong when you run it