Rationale for using `buildSrc` instead of `Composite Builds`

[om-ha]

PeopleInSpace uses Build Sources (buildSrc).

Is there a reason why Composite Builds is not used instead?

As I was checking how PeopleInSpace manages versioning, I saw this PR #116 and it prompted me to look into buildSrc and Composite Build.

[vitorhugods]

While I'm not John, my 2 cents:
Composite builds are not supported by IntelliJ on Multiplatform projects, and it leads to tons of unresolved references starting in Kotlin 1.6.21 with Hierarchical Project Structures.

People at Apollo have come up with a work-around, that still has some drawbacks, like IDE Sync being slow as it rebuilds from scratch every time.

My advise, as someone using composite builds and KMM is: avoid this combination if you can.

This should be improved in the future, but it's not stable for now.