Le 23/09/2026 à 11:31, Vladimir Petko a écrit :
I did come across the paper that describes an interesting approach. It claims that we can have reproducible results by having the LLM harness generate refactoring recipes[1] rather than directly patching the source code. This also saves tokens, as a single recipe (such as dropping all instances of the dokka plugin) can be applied across multiple packages.
Interesting idea, if you have to patch a high number of packages I guess it saves tokens. But in this case I prefer patching the library to restore the compatibility (as we do with Guava and Bouncy Castle).
I was also wondering if moving from maven.rules / maven.ignoreRules to publishing relocation POMs could simplify things. This allows the agent to work directly with the prepared Maven repository and the source tree without struggling with the Gradle plugin that rewrites the artifact coordinates.
The last time I checked Gradle didn't support relocation POMs.
The Kotlin DSL requires Kotlin that requires Intellij IDEA Platform that requires Bazel. Bazel was recently upgraded to 7.7.1 (which is a great news) , but we need 9 for Intellij IDEA ;( Since those are not backwards compatible I was wondering if the goal is to have 9 as the bazel-bootstrap or we will need a versioned package?
Bazel was introduced "recently" (in 2024), it doesn't come into the picture before Kotlin 2.3.20 and Gradle 9.5. We haven't reached this point yet.
Emmanuel Bourg
