This message was deleted.

You should probably not have one mega-build, but several builds that you combine in a composite build. Then the dependencies are also on the coordinates and you should not have a problem, no?

Well, it's a composite build I'm heading for already, so I basically miss a way to let Gradle know that I want to fetch the Android "flavor-1" from "foo" like so

implementation("my.company:foo@flavor-1")

I'm not too familiar with Android, but didn't you say you publish the variants under separate artifact coordinates? Maybe you could also consider publishing them as feature variants instead.

Hrm, I guess Android library variants are incompatible with Gradle's / Maven's classifiers (otherwise I could use the

@flavor-1

notation above). I now resorted to creating a couple of modules with specific names, so I can actually depend on them properly across components.

Yeah, using classifiers with composite builds does not work I think. For that you need proper feature variants iirc.