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

Consider Using Gradle Version Catalogs #256

Closed
ccjernigan opened this issue Aug 29, 2021 · 0 comments · Fixed by #286
Closed

Consider Using Gradle Version Catalogs #256

ccjernigan opened this issue Aug 29, 2021 · 0 comments · Fixed by #286
Assignees

Comments

@ccjernigan
Copy link
Contributor

What is your feature request?
Use Gradle Version Catalogs to manage dependencies.

How would this feature help you?
This would leverage a standard way to manage dependency versions, which should make it easier for new contributors to understand how our project is set up. It also removes a plugin from the critical path of our build system.

Because Version Catalogs are an incubating feature, this is not necessarily an immediate feature request.

There are two different version catalog approaches, one using settings.gradle and the other using a toml file. It isn't clear which will ultimately be the right approach, although switching that should be relatively straightforward because the typesafe version accessors are still the same in the rest of the build scripts.

ccjernigan added a commit that referenced this issue Sep 25, 2021
This will provide reports on dependecy updates that are available.

Its outside the critical path of the build, so it can be readily disabled or replaced in the future.
@ccjernigan ccjernigan linked a pull request Sep 25, 2021 that will close this issue
@pacu pacu closed this as completed in #286 Sep 27, 2021
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

Successfully merging a pull request may close this issue.

1 participant