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.

Sign up for GitHub

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

Jump to bottom

Use a version catalog to sync module dependency versions #78

Open

jakaarl opened this issue Aug 2, 2023 · 1 comment

Assignees

Labels

Contributor

jakaarl commented Aug 2, 2023

Backend and related modules depend on libraries which need to be kept in sync. We should define the common versions in a catalog, publish it and consume it in each module. See: https://docs.gradle.org/current/userguide/platforms.html#sec:sharing-catalogs

jakaarl added the enhancement label

Contributor

pveeckhout commented Aug 3, 2023 •

edited

Loading

Personally I am much more inclined to use a platform rather than a catalog.

the platform is more heavyweight, but it also works on transitive dependencies, but I feel it might serve our case better

https://docs.gradle.org/current/userguide/platforms.html#sub:platforms-vs-catalog

we can both use a catalog and declare a platform which itself uses the catalog:

jakaarl self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment