The binary-compatibility-validator API module published on Maven central does not declare dependency on ASM and kotlin-metadata-jvm

[mikaelstaldal]

The binary-compatibility-validator API module published on Maven central does not declare dependency on org.ow2.asm:asm, org.ow2.asm:asm-tree, org.jetbrains.kotlin:kotlin-metadata-jvm.

[fzhinkin]

At the moment, there's no separate binary-compatibility-validator API module.
org.jetbrains.kotlinx:binary-compatibility-validator is the Gradle plugin's implementation, and dependencies on ASM and kotlin-metadata-jvm are managed by the means of Gradle configurations. Dependencies are declared that way intentionally, to prevent their leakage into projects applying the BCV plugin.

There was a plan to split the plugin and publish separate artifacts providing an API for validation. However, currently the plugin is migrating into Kotlin repository (#223) and an API might be provided there eventually.

[mikaelstaldal]

At the moment, there's no separate binary-compatibility-validator API module.

So how come I found this? https://central.sonatype.com/artifact/org.jetbrains.kotlinx/binary-compatibility-validator/0.16.3/overview

[fzhinkin]

So how come I found this? https://central.sonatype.com/artifact/org.jetbrains.kotlinx/binary-compatibility-validator/0.16.3/overview

As I wrote:

org.jetbrains.kotlinx:binary-compatibility-validator is the Gradle plugin's implementation

That does not contradict the fact that it comes bundled with an API. However, it is not a standalone library, thus its dependencies are managed they way they are managed.

[mikaelstaldal]

So how come I found this? https://central.sonatype.com/artifact/org.jetbrains.kotlinx/binary-compatibility-validator/0.16.3/overview

As I wrote:

org.jetbrains.kotlinx:binary-compatibility-validator is the Gradle plugin's implementation

That does not contradict the fact that it comes bundled with an API. However, it is not a standalone library, thus its dependencies are managed they way they are managed.

How am someone who stumble upon it on Maven Central supposed to know it's not a standalone library?

[fzhinkin]

How am someone who stumble upon it on Maven Central supposed to know it's not a standalone library?

There's a link to this repository, and it is clearly stated that BCV is a Gradle plugin.

But yeah, artifact's description could be improved.

[fzhinkin]

And we should also include details on required additional dependencies for those who use the plugin as a library.

[mikaelstaldal]

It seems like the kotlinx.validation.api package doesn't have any Gradle dependencies, so that package can be considered a library. What about actually releasing that as a proper library (with correct dependencies)? Should be quite easy to do I think.

[fzhinkin]

Currently, BCV is migrating to the Kotlin repository (#223, https://youtrack.jetbrains.com/issue/KT-71098); the split into a plugin and a separate library most likely will happen after the migration complete.

[mikaelstaldal]

Currently, BCV is migrating to the Kotlin repository (#223, https://youtrack.jetbrains.com/issue/KT-71098); the split into a plugin and a separate library most likely will happen after the migration complete.

Sounds good. In the mean time, I and others will use the current Gradle plugin module as a library