-
-
Notifications
You must be signed in to change notification settings - Fork 777
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
Make a release built against Kotlin 1.4 #2974
Comments
Getting rid of the warning will also require a new Gradle release, won't it? Kotlin 1.4 support is on the way (#2931). Unfortunately we are blocked by pinterest/ktlint#830. |
Hmm, that triggers a good question for me: I actually don't want to enforce the Kotlin version on the Gradle / pluging classpath, but only on our app's compile classpath. So maybe the
simply is too broad and affects the plugin classpath, too... I need to look into this. |
Buildscript (plugin) and project classpath is separated (mostly), however, certain plugins (like e.g. the kotlin allopen plugin) might require the same Kotlin version on both classpaths. In any case, your issue @sschuberth might be resolved by this: configurations.all {
resolutionStrategy.eachDependency {
if (requested.group == "org.jetbrains.kotlin" && requested.name == "kotlin-reflect") {
useVersion("1.4.0")
}
}
} Most likely because some runtime dependency pulls in kotlin-reflect transitively (moshi-kotlin e.g. does it). |
Thanks @realdadfish for the idea. I'm doing something similar but more detekt-specific currently, see oss-review-toolkit/ort@6976ae0#diff-392475fdf2bc320d17762ed97109a121R176 |
FYI, ktlint 0.38.0 final has just been released with the fix: https://github.com/pinterest/ktlint/releases/tag/0.38.0 |
I think we need to wait for a 0.38.1 and also build with language version = |
Context
Kotlin 1.4 was released and we'd like to update to it, but we cannot as the compiler would issue a warning (and we break on warnings) due to detekt being built against Kotlin 1.3.72, and we cannot enforce Kotlin 1.4 due to this issue.
The text was updated successfully, but these errors were encountered: