-
Notifications
You must be signed in to change notification settings - Fork 413
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
Incompatibility with Kotlin v2 #3788
Comments
I dont think this has anything to do with Kotlin, and is likely caused by an outdated gradle plugin (usually the foojay resolver), or an incorrect multi project setup. |
Don't see it in my Gradle Build; dunno what would be incorrect about the multi-project setup. It succeeds on previous Kotlin versions, so there might be something there. |
There is a Gradle bug that allows other Gradle plugins to pull in an older version of shared transitive dependenies such as gson. You should make sure that you define all of your plugin versions in the root project, as documented here: https://docs.gradle.org/current/userguide/plugins.html#sec:subprojects_plugins_dsl |
If that was true, why would it work on older Kotlin versions? The only thing that changed is the |
Im not sure why this happens, this error happens when loom does not have the correct version of GSON on the classpath even though it correctly depends on a newer version. FLK is building fine with Kotlin 2 |
👋 We use the issue tracker exclusively for final bug reports and feature requests. However, this issue appears to be better suited for either a discussion thread, or a message on our discord server. Please post your request on one of these, and the conversation can continue there. |
Dependabot PR on GitHub Actions reporting issues when upgrading from Kotlin
1.9.24
to2.0.0
.Tried rerunning it to see if it was something on my build, then tried rerunning it on the previous Kotlin version; the former failed and the latter succeeded, which might mean something changed in Kotlin v2. Pretty sure but not 100%.
Gradle File: here
Actions Logs: here
The text was updated successfully, but these errors were encountered: