kover is a tricky dependency. Between versions 0.6. and 0.7. its gradle API changed a lot. And so happened that this change took place with the change of their Kotlin version from 1.6.0 compatible to 1.8.0 compatible. That means that we cannot use its API in kotlin builds with Kotlin lower than 1.8.0.
The solution is to load kover configuring scripts dynamically, which is done by loading one of precompiled gradle plugins. They both have the same id, the only difference it that only one of them configures kover, and other does nothing (for versions 1.7.*). As we use kover only in a separate build with the latest Kotlin version, this should be a good enough solution
kover
is a tricky dependency. Between versions 0.6. and 0.7. its gradle API changed a lot. And so happened that this change took place with the change of their Kotlin version from1.6.0
compatible to1.8.0
compatible. That means that we cannot use its API in kotlin builds with Kotlin lower than1.8.0
.The solution is to load
kover
configuring scripts dynamically, which is done by loading one of precompiled gradle plugins. They both have the same id, the only difference it that only one of them configures kover, and other does nothing (for versions 1.7.*). As we use kover only in a separate build with the latest Kotlin version, this should be a good enough solutionFYI: Also added corresponding TC build check