https://kotlinlang.org
Join Slack
Something's very funny... I have a version catalog referring to Kotlin 1.9.22 and the ksp version co...
# gradle
d
Something's very funny... I have a version catalog referring to Kotlin 1.9.22 and the ksp version corresponding to it, but ksp seems to give me an error that I'm using 1.9.21... configs in the thread
Copy code
[plugins]

jib = { id = "com.google.cloud.tools.jib", version.ref = "jib" }

kotlin-jvm = { id = "org.jetbrains.kotlin.jvm", version.ref = "kotlin" }
ksp = { id = "com.google.devtools.ksp", version.ref = "ksp"}

[versions]

ksp = "1.9.22-1.0.17"
##⬆= "2.0.0-Beta1-1.0.14"
##⬆= "2.0.0-Beta1-1.0.15"
##⬆= "2.0.0-Beta2-1.0.16"
##⬆= "2.0.0-Beta3-1.0.17"

jib = "3.4.0"

kotlin = "1.9.22"
I even tried using a fixed version:
Copy code
plugins {
    alias(libs.plugins.jib)
    application
    alias(libs.plugins.kotlin.jvm) version "1.9.22"
    alias(libs.plugins.ksp)
}
But I get:
Configure project :
Copy code
ksp-1.9.22-1.0.17 is too new for kotlin-1.9.21. Please upgrade kotlin-gradle-plugin to 1.9.22.
ksp-1.9.22-1.0.17 is too new for kotlin-1.9.21. Please upgrade kotlin-gradle-plugin to 1.9.22.
ksp-1.9.22-1.0.17 is too new for kotlin-1.9.21. Please upgrade kotlin-gradle-plugin to 1.9.22.
ksp-1.9.22-1.0.17 is too new for kotlin-1.9.21. Please upgrade kotlin-gradle-plugin to 1.9.22.
This happens even when running 
./gradlew test
from the command line
v
Can you share a build 
--scan
?
The scan also confirms you use 1.9.21. It also looks like you use 
kotlin-dsl
, right? Then you should not choose an arbitrary Kotlin version anyway. Gradle controls the runtime environment, so you should also stick to that in the build environment.
d
I'm not making a gradle plugin... I'm just compiling a regular ktor project.
My plugins block is exactly what I posted above, and it's not even a multi module project...
From what I understand, you're talking about when making a gradle plugin with 
kotlin-dsl
and Gradle has 1.9.21 embedded in it... but it shouldn't affect the actual project code... maybe the test code is affected since gradle is running it?
It doesn't really make sense though, since I don't think I encountered this problem before...
@Vampire?
v
Sorry, I also have to do some real work, I'm just a Gradle user like you with a regular fulltime job, trying to help. 😉
But yeah, I might have misinterpreted the build scan then.
No idea then, as the build scan also does not say that 1.9.22 was requested but downgraded to 1.9.21
It looks like right away 1.9.21 of the plugin was requested
Unless you have some resolution strategy with 
force
which would then look like that iirc
d
Of course, really appreciate your time 😄! I just assumed that you might just not have seen my answer -- I downgraded to 1.9.21 and the message dissappeared... I was just wondering what happened 🤔.
v
Hard to say without seeing the build. Maybe you can try to knit an MCVE
Often that already discovers the problem by just trying to boil down an MCVE
👍🏼 1
t
KGP tries to align all the plugin dependencies versions via platform. Could you share the build scan as well?
165 Views
Open in Slack
PreviousNext
Powered by

kotlinlang

A modern programming language that makes developers happier.

Powered by