On 0.15.0-Beta.3, the plugin generates an empty klib.api if the module only supports Android/JVM targets. This causes the binary compatibility check to fail with the error Project ABI file XYZ.klib.api is empty.. The release notes mention adding modules to ignoredProjects, but I believe that also disables checking the android/XYZ.api and jvm/XYZ.api files. I have the new klib validation support enabled with strictValidation = true:
klib {
enabled = true
strictValidation = true
}
To reproduce:
Run ./gradlew apiDump and then ./gradlew apiCheck in this project. I can make a smaller repro project if needed.
On
0.15.0-Beta.3, the plugin generates an emptyklib.apiif the module only supports Android/JVM targets. This causes the binary compatibility check to fail with the errorProject ABI file XYZ.klib.api is empty.. The release notes mention adding modules toignoredProjects, but I believe that also disables checking theandroid/XYZ.apiandjvm/XYZ.apifiles. I have the new klib validation support enabled withstrictValidation = true:klib { enabled = true strictValidation = true }To reproduce:
Run
./gradlew apiDumpand then./gradlew apiCheckin this project. I can make a smaller repro project if needed.