Use version catelogs in Gradle#276
Closed
Yang-33 wants to merge 2 commits into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version catalogs is a modern way to declare versions. https://docs.gradle.org/current/userguide/version_catalogs.html
This change migrates the current version declarations to version catalogs. The scope of this change is only aliases, so it does not affect publishing or dependency resolution.
Version catalog can also manage plugin versions, but I did not introduce that yet because the current
build.gradlestyle cannot use it. After we finish cleaning up the Gradle setup, we may be able to introduce it.I confirmed that this does not change version resolution or the published JARs as follows: