Moving ABI Validation to Kotlin Gradle Plugin

[shanshin]

This is an issue to discuss the Moving ABI Validation to Kotlin Gradle Plugin proposal. The text of the proposal is located here.

[kyay10]

This is merely about moving it to the KGP, right? If so, that's a net positive. I think we're severly in need of https://youtrack.jetbrains.com/issue/KT-78299 though, since sometimes it's hard to figure out what's binary compatible and what isn't (and declarations in the dump files move around very easily, from something as simple as changing a final to an open)

[shanshin]

Yes, this KEEP just about migrating the existing features from a separate Gradle plugin to Kotlin Gradle Plugin.
In his scope, adding new functionality is not considered, it only describes in general terms what we will do after migration (this section).

[CLOVIS-AI]

The main downside I see here is that making KGP bigger will make it slower to adopt new best practices (configuration cache, isolated projects support…). Today, KGP is quite fragile, especially when it comes to multiplatform development, and APIs are often removed without replacement.

Is there a plan to mitigate this risk while implementing this proposal?

Other than that, this proposal seems very convenient and a good simplification for end users 👍

[shanshin]

will make it slower to adopt new best practices

The code is already migrated taking these approaches into account, so it does not affect KGP directly.

APIs are often removed without replacement

The DSL for BCV is minimally related to the DSL of KGP, they can be changed independently of each other if necessary.