I m trying to upgrade Kotlin to 1 7 0 and I m no longer able

Question

I m trying to upgrade Kotlin to 1 7 0 and I m no longer able to get my `buildSrc` project to configure It s breaking on applying the `kotlin dsl` plugin ```An exception occurred applying plugin request id org gradle kotlin kotlin dsl version 2 3 3 gt Failed to apply plugin class org jetbrains kotlin gradle plugin KotlinPluginWrapper gt Could not create an instance of type org jetbrains kotlin gradle dsl KotlinJvmProjectExtension gt Companion``` Gradle version 7 3 3 Kotlin version 1 7 0 kotlin dsl version 2 2 and 2 3 3

mkrussel · Answer

Some of the stack trace ```Caused by java lang NoSuchFieldError Companion at org jetbrains kotlin gradle dsl ToolchainSupport$Companion createToolchain$kotlin gradle plugin ToolchainDsl kt 33 at org jetbrains kotlin gradle dsl KotlinTopLevelExtension lt init gt KotlinProjectExtension kt 69 at org jetbrains kotlin gradle dsl KotlinProjectExtension lt init gt KotlinProjectExtension kt 109 at org jetbrains kotlin gradle dsl KotlinSingleTargetExtension lt init gt KotlinProjectExtension kt 118 at org jetbrains kotlin gradle dsl KotlinSingleJavaTargetExtension lt init gt KotlinProjectExtension kt 124 at org jetbrains kotlin gradle dsl KotlinJvmProjectExtension lt init gt KotlinProjectExtension kt 128 at org jetbrains kotlin gradle dsl KotlinJvmProjectExtension Decorated lt init gt Unknown Source at java base jdk internal reflect NativeConstructorAccessorImpl newInstance0 Native Method at java base jdk internal reflect NativeConstructorAccessorImpl newInstance NativeConstructorAccessorImpl java 62 at java base jdk internal reflect DelegatingConstructorAccessorImpl newInstance DelegatingConstructorAccessorImpl java 45 at org gradle internal instantiation generator AsmBackedClassGenerator$InvokeConstructorStrategy newInstance AsmBackedClassGenerator java 2070 at org gradle internal instantiation generator AbstractClassGenerator$GeneratedClassImpl$GeneratedConstructorImpl newInstance AbstractClassGenerator java 488 at org gradle internal instantiation generator DependencyInjectingInstantiator doCreate DependencyInjectingInstantiator java 64 311 more```

mbonnin · Answer

You can t really use 1 7 0 in `buildSrc` because Gradle uses something else 1 5 most likely Your best bet is to use ```plugins `embedded kotlin` ``` or ```plugins `kotlin dsl` ```

mbonnin · Answer

Oh wait looks like this is what you re doing already thinking face

mbonnin · Answer

Can you build your `buildSrc` project separately ``` gradlew p buildSrc build```

mkrussel · Answer

no I also tried adding the `embedded kotlin` plugin but still no luck When I did revert back to 1 6 21 the warning about incompatible kotlin versions went away but I still cannot build with 1 7 0

mbonnin · Answer

`buildSrc` should know nothing about 1 6 vs 1 7

mbonnin · Answer

``kotlin dsl`` will choose the correct version of Kotlin to use based on your Gradle version

mbonnin · Answer

If you have a manually defined Kotlin version in `buildSrc` that s most likely the cause of your error

mkrussel · Answer

I have not defined in in `buildSrc` but I do use ```kotlin plugin serialization version 1 6 21 ``` in the plugins

mbonnin · Answer

I guess that s in a convention plugin somewhere

mkrussel · Answer

Yes

mbonnin · Answer

```buildSrc src main kotlin my convention gradle kts``` or so

mkrussel · Answer

Does the version of dependencies for the actual source code impact what is used when loading the plugins

mbonnin · Answer

Define actual sweat smile

mkrussel · Answer

Actually everything in the `buildSrc` are ` kt` files no ` kts` files

mbonnin · Answer

<https docs gradle org current samples sample convention plugins html compiling convention plugins> points at ` kts` files but maybe it s not important

mkrussel · Answer

Actual being what is declared in the dependency section of the gradle file but not the buildscript dependencies So the dependencies that the Kotlin source code links with

mbonnin · Answer

I mean you have multiple gradle files and buildscript there so it s hard to tell

mbonnin · Answer

What I d do is move from `kotlin dsl` to `embedded kotlin` and rewrite the convention plugins as regular ` kt` files it might be easier to see where the problem is

mbonnin · Answer

Plus you d save some build time

mkrussel · Answer

It was the dependencies when I downgraded them all to ones that use an older version of kotlin the error goes away

mkrussel · Answer

Thanks for all your help

mbonnin · Answer

Sure thing Glad you found a solution

mikehearn · Answer

This is the same problem discussed earlier in this channel <https kotlinlang slack com archives C19FD9681 p1656593570021959>

mikehearn · Answer

There seems to be no way to upgrade to Kotlin 1 7 currently when using the standard project layout created according to the Gradle docs because the kotlin version used by the project and by the build get conflated

mbonnin · Answer

< mikehearn> do you have a reproducer I m pretty sure you can use 1 7 in your main build while still using the embedded Kotlin version for your `buildSrc` `convention plugins`

mikehearn · Answer

In the thread above a whole lot of people worked with me on it and we got nowhere It never worked It did result in a PR to the gradle docs but the underlying issue remains There s no obvious way to specify a version of Kotlin for your project but not the build script the attempts I made all failed with different errors disappointed

mikehearn · Answer

mkrussel seems to reach the same point as me he downgrades to older kotlin again

mbonnin · Answer

How do I reproduce Follow the steps at <https docs gradle org current samples sample building kotlin applications multi project html> and bump the kotlin version

mbonnin · Answer

Working well for me <https github com martinbonnin demo commit 28e73ad0949cf0467e40f93bf729c70814707a33>

mbonnin · Answer

```mbonnin ~ git demo$ gradlew app run gt Task app run Hello World 1 7 0 BUILD SUCCESSFUL in 484ms```

mikehearn · Answer

The issue is caused by common plugins

mikehearn · Answer

The thread above ends with sort of concluding that there s some plugin that is causing conflicts because it depends on kotlin but there s no easy way to figure out which one So we wait for Gradle to upgrade Kotlin to 1 7 and hope the issue goes away

mikehearn · Answer

Or something like that Don t quite recall It seems like a common problem though

mbonnin · Answer

In that case yes but it s an issue from a specific plugin not a general issue with 1 7

mikehearn · Answer

Right Kotlin itself is fine but lots of projects are stuck due to this issue I shared the build gradle kts before and even disabled some plugins but it didn t help the only ones left are all common like dokka Could try again soon and see if there are many new plugin versions that fix it but for now we gave up It s too hard to upgrade Kotlin with Gradle and when things break the errors don t help disappointed

mbonnin · Answer

FWIW we shadow `kotlin stdlib` in our plugins to avoid exactly that issue I wrote about it there <https blog mbonnin net use latest kotlin in your gradle plugins>

mbonnin · Answer

If you have a specific plugin that doesn t work it s worth opening an issue there as it s fixable workaroundable

mbonnin · Answer

I know that situation is far from ideal but getting stuck on older versions of Kotlin isn t ideal either

mikehearn · Answer

Problem was I couldn t figure out which was doing it Disabling more and more plugins is one way but then that would just break the build as parts do depend on those plugins

mbonnin · Answer

Can you share all your plugins with versions

mikehearn · Answer

<https gist github com mikehearn 4c2a5ccfb3d222fa28805cf12b2c53e0> NB The powerassert and arrow analysis plugins are were known to not work on 1 7 but even with them disabled there was no difference Generally all the obviously optional ones were commented out and disabled but no dice

mbonnin · Answer

Perfect ok hand

mbonnin · Answer

You can see the dependencies with ` gradlew p buildSrc dependencies` that should show which one is pulling Kotlin 1 7

mbonnin · Answer

In that specific case `kotlin reflect` is pulling `kotlin stdlib 1 7 0`

mbonnin · Answer

You can either remove kotlin reflect from your dependencies or workaround by disabling the metadata version check ```tasks withType org jetbrains kotlin gradle tasks KotlinCompile class java kotlinOptions freeCompilerArgs = freeCompilerArgs + Xskip metadata version check ```

mikehearn · Answer

Ah this rings a bell Refreshing my memory from the other thread I wrote this gt OK partial success After removing that reflect line and the three plugins I can get a build with Kotlin 1 7 woop Thanks Unfortunately re enabling Dokka and upgrading it to Dokka 1 7 0 brings back the same metadata version mismatch error as before So it seemed at the time we have to choose between Dokka and Kotlin 1 7 and Dokka is more important Perhaps there s been a new release since that fixes this

mikehearn · Answer

This was only two weeks ago though

mbonnin · Answer

Yea just tried with dokka and for some reason 1 7 10 still pulls the stdlib disappointed

mbonnin · Answer

So somewhat looks like <https github com Kotlin dokka pull 2543|my fix> didn t work thinking face

mikehearn · Answer

I should commit the removed reflect dep anyway though thx for the reminder I think I just got frustrated and rolled everything back as by that point the build was pretty hacked up

mbonnin · Answer

Something s weird with the dokka 1 7 10 release thinking face I don t have the issue if I build locally

mbonnin · Answer

Or maybe something s weird with my local setup Investingating I ll update this thread

mikehearn · Answer

Thanks

mbonnin · Answer

Fun stuff the dokka 1 7 10 from `mavenCentral ` isn t the same as the dokka 1 7 10 from `gradlePluginPortal `

mikehearn · Answer

Oof disappointed

Ignat Beresnev · Answer

Hi Yeah sorry to hear Dokka is getting in the way You can have a look at the issue there s some workarounds <https github com Kotlin dokka issues 2546|https github com Kotlin dokka issues 2546>

mikehearn · Answer

Thanks I think we ll wait 1 7 is a nice upgrade but not urgent Once it s all sorted out then we ll try again

mbonnin · Answer

For Dokka you can use dokka 1 7 10 and do the following ```repositories mavenCentral gradlePluginPortal content Might not even be needed since mavenCentral should take precedence excludeGroup org jetbrains dokka ```

mbonnin · Answer

That + removing the kotlin reflect line should make your project compile

mbonnin · Answer

I filed <https github com arrow kt arrow analysis issues 51|this issue> on Arrow but this is only warnings I think it shouldn t prevent you to build

mbonnin · Answer

If you ever have another issue please report them the sooner we get them fixed the sooner the ecosystem can move forward

mikehearn · Answer

Thanks

mikehearn · Answer

I ll try that soon

mbonnin · Answer

In other news Gradle 7 5 is out tada <https docs gradle org 7 5 release notes html>

Ignat Beresnev · Answer

Updating to it also solves the problem right

mbonnin · Answer

Yep most likely Gradle 7 5 with embedded Kotlin 1 6 can read the Kotlin 1 7 metadata

mbonnin · Answer

Because there s a 1 version forward compatibility

mbonnin · Answer