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

Use Gradle version catalogs to have a single source of truth for dependency versions #1594

Open
calebkiage opened this issue Sep 30, 2024 · 2 comments

Comments

@calebkiage
Copy link

calebkiage commented Sep 30, 2024

I propose using Gradle's version catalogs to have a single source of truth for the project's dependency versions and also (hopefully) reduce the number of dependabot PRs for the same dependency in the project.
This feature should also be supported by gradle 8.9 which this project uses. See https://docs.gradle.org/8.9/userguide/platforms.html

@github-project-automation github-project-automation bot moved this to Needs Triage 🔍 in Kiota Sep 30, 2024
@baywet
Copy link
Member

baywet commented Sep 30, 2024

Hey @calebkiage
We're already using that to share dependencies between main/java-8/android projects for each package.
I don't think we can use it across packages since they have different dependencies (e.g. azure identity authentication provider needs azure core that's not needed in other packages)

Can you provide more information on how you'd use this feature in addition to the current configuration please?

@baywet
Copy link
Member

baywet commented Sep 30, 2024

Ah scratch the last comment, I thought we were referring to a dependencies catalog, but eventually clicked on the link.
Yes a version catalog would be interesting. We should double check that dependenbot supports it first though.

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

No branches or pull requests

2 participants