You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Spring Boot app, jvmTarget 11, Kotlin 1.5.32 and with Detekt 1.19.0. Running ./gradlew --debug detekt works without problem. After upgrading to 1.20.0 I would expect it to continue to run.
Observed Behavior
With version 1.20.0 I get the error:
...
[ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception.
[ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
[ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong:
[ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Execution failed for task ':detekt'.
[ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] > Invalid value passed to --jvm-target
I tried with various versions of Kotlin and only 1.6.20 and 1.6.21 worked:
1.5.31 -> Failed
1.5.32 -> Failed
1.6.0 -> Failed
1.6.10 -> Failed
1.6.20 -> OK
1.6.21 -> OK
Your Environment
Version of detekt used: 1.20.0
Version of Gradle used: 7.2
Operating System and version: Windows 10
Version of Kotlin used: 1.5.32
The text was updated successfully, but these errors were encountered:
If you're diverging from those versions, things might not work properly. If you're using the Gradle Plugin, that's even more likely due to how Gradle embeds a Kotlin version in its runtime.
Moreover, this issue has been already discussed here: #4786
Closing as it's essentially a duplicate. Feel free to re-opne if you have more context to share.
Expected Behavior
I have a Spring Boot app, jvmTarget 11, Kotlin 1.5.32 and with Detekt 1.19.0. Running
./gradlew --debug detekt
works without problem. After upgrading to 1.20.0 I would expect it to continue to run.Observed Behavior
With version 1.20.0 I get the error:
I tried with various versions of Kotlin and only 1.6.20 and 1.6.21 worked:
1.5.31 -> Failed
1.5.32 -> Failed
1.6.0 -> Failed
1.6.10 -> Failed
1.6.20 -> OK
1.6.21 -> OK
Your Environment
The text was updated successfully, but these errors were encountered: