@Elena Lepilkina Not the exact reason, but I think it was linked to a custom settings Gradle plugin managing the versions via
pluginManagement
which were pulled from an external file, and I think the result of the first
pluginManagement
run was being cached by Gradle, which made it keep using an older Kotlin Gradle plugin.
I improved this plugin a lot since then and I've not encountered the issue again so far, but I can try to reproduce it if you give me hints on how to do it.
e
Elena Lepilkina
10/21/2020, 9:21 AM
I also had an idea that it should be connected with some custom settings in Gradle and Gradle cashes.
I can try to reproduce it if you give me hints on how to do it.
Thank you! But I think there is no need in this now, we'll wait @Merseyside answer. If your reproducer is needed later, I'll let you know.