Good evening,

Work resumed on kotlin2. At this point I'm still trying to get its build script to compile in offline mode, while identifying the dependencies and eventually replacing them or patching them out of the build scripts.

This is sometimes complicated by limitations or maybe bugs in Gradle: right now I have to figure out why it fails to resolve the kotlin stdlib when version substitution is applied, and beyond that why it now fails to resolve (from the root settings.gradle that is still a Groovy script) a Kotlin class that is confirmed to be present in a plugin that is supposed to be already loaded.

Fortunately these failures occur early in the build settings evaluation phase so trial cycles are still short. I though that Kotlin build infrastructure was smaller than that of Gradle but it's actually about 3 times larger, though I think the full project builds a bit faster.

The way the build scripts are structured and the set of used Gradle features is also slightly different so I have to modify my custom build plugin that replaces artifact repositories and selectively rewrites dependencies coordinates and then debug it when hitting new issues such as above.

Meanwhile in California, upstream Gradle 8.14 was released today.

A thank you to werdahias that offered to help on IRC a few hours ago. Right now I don't have an up-to-date wishlist of packages that could be worked on (updated, or created) but I will work on that as I progress on kotlin2; for gradle most missing or outdated packages need newer versions of gradle/kotlin/groovy to be built.

Cheers,

--
Julien Plissonneau Duquène

Reply via email to