Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rationale for using buildSrc instead of Composite Builds #117

Open
om-ha opened this issue Feb 21, 2022 · 1 comment
Open

Rationale for using buildSrc instead of Composite Builds #117

om-ha opened this issue Feb 21, 2022 · 1 comment

Comments

@om-ha
Copy link

om-ha commented Feb 21, 2022

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.

@om-ha om-ha changed the title Rationale buildSrc instead of Composite Builds Rationale for using buildSrc instead of Composite Builds Feb 21, 2022
@vitorhugods
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants