-
-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support jvmTarget 17 #4287
Comments
It seems like the issue is that I tried doing this in an included build. It works fine otherwise. Not sure why it doesn't work in included builds, but I'm guessing it's not a detekt issue. |
This project has a I just ran into this issue in another project that tries to use Maybe there is something going on here? |
Here's my config:
|
Kotlin 1.5.3X seems to support up to Java 16 as the target: https://github.com/JetBrains/kotlin/blob/1.5.30/compiler/config.jvm/src/org/jetbrains/kotlin/config/JvmTarget.kt. I see that JVM_17 was added in Kotlin 1.6.0, so hopefully this is unblocked by #4277 |
Working workaround: dependencies {
detekt("io.gitlab.arturbosch.detekt:detekt-cli:1.19.0")
detekt("org.jetbrains.kotlin:kotlin-compiler-embeddable:1.6.0")
} |
Looks like the issue is that the snapshots aren't updated since November. |
Not sure what you refer to, but the last snapshot was published today: |
Ah I was looking at a different view of the snapshot repo. Well then this is still an issue. Like I said above:
|
Do you have a complete reproducer to share? It shouldn't matter that detekt is setup in a precompiled script plugin - the classpath used by detekt when it runs should be isolated from that used by Gradle. We can verify with a build scan (that would also help in the absence of a complete repro). |
I'm working on putting something together. It also could be that I have custom rules that are on an older version of detekt, so I'm going to try to update those first. |
False alarm, it was only happening when I used It's a little odd because I made a fresh project with all of the same configuration and it didn't have this issue. Maybe something weird got stuck in the cache. Update Updating my project to Kotlin 1.6.20 from 1.6.10 solved the issue. Still weird because the fresh project was also using 1.6.10 and didn't fail. |
Currently setting it to 17 results in
Invalid value passed to --jvm-target
The text was updated successfully, but these errors were encountered: