Support jvmTarget 17
See original GitHub issueCurrently setting it to 17 results in Invalid value passed to --jvm-target
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:12 (9 by maintainers)
Top Results From Across the Web
Support for targetRelease=17 : KT-49564 - JetBrains YouTrack
e: Unknown JVM target version: 17. Supported versions: 1.6, 1.8, 9, 10, 11, 12, 13, 14, 15, 16. (tried with kotlin 1.6.0-RC2). Activity...
Read more >Gradle | Kotlin
Gradle. Gradle is a build system that helps to automate and manage your building process. It downloads required dependencies, packages your ...
Read more >why gradle kotlin plugin does not provide jvmTarget ... - Reddit
with java gradle plugin i can just do java { sourceCompatibility = JavaVersion.VERSION_17 targetCompatibility = JavaVersion.VERSION_17. }.
Read more >android - Cannot inline bytecode built with JVM target 1.8 into ...
VERSION_1_8 } kotlinOptions { jvmTarget = JavaVersion. ... this: File > Setting > Kotlin Compiler > Target JVM Version > 1.8 did not...
Read more >Why and How to Upgrade to Java 16 or 17 - InfoQ
Java 17, the next Long Term Support (LTS) release, ... Gradle won't build your project and Kotlin cannot use jvmTarget = "17" ....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Working workaround:
False alarm, it was only happening when I used
main-SNAPSHOT, and it looks like the issue is that I settoolVersionto the same version that I use for the dependency, and it didn’t like usingmain-SNAPSHOTfor that. So I changedtoolVersionto use1.20.0-RC2and then it worked.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.