IssueTracker

Came across this question when enabling KMP for window-core, but this generally applies to most projects that compose-desktop depends on or vice-versa.

Currently, androidx has a few projects which enable desktop() and android() variants, which can have different sourcesets for JVM or Android targets, but Metalava only generates a single copy of api files to track "both". It's unclear which subset of sources it tracks between common, jvm and android, but likely the correct solution is to have multiple copies of API files similar to kotlin's binary-compatibility-validator.

A good example is androidx.compose.material:material-ripple, they have android specific sources, but only one set of API files and it is unclear whether it's jvm or android that is tracked.