You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've observed that many dependencies in our build.gradle and settings.gradle files have hard-coded version numbers. To streamline the process of managing these versions, I propose that we move all version numbers to a gradle version catalog file. This change would allow us to easily upgrade or downgrade versions from a single location, improving maintainability and reducing the risk of inconsistencies.
The text was updated successfully, but these errors were encountered:
ThatSilentCoder
changed the title
Include dependency versions in gradle.properties file
Write Dependencies' Version Numbers in gradle.properties file
Oct 29, 2024
ThatSilentCoder
changed the title
Write Dependencies' Version Numbers in gradle.properties file
Write Dependencies' Version Numbers in Versions.toml file
Nov 22, 2024
ThatSilentCoder
changed the title
Write Dependencies' Version Numbers in Versions.toml file
Place Dependencies in a Version Catalog file
Nov 22, 2024
I've observed that many dependencies in our build.gradle and settings.gradle files have hard-coded version numbers. To streamline the process of managing these versions, I propose that we move all version numbers to a gradle version catalog file. This change would allow us to easily upgrade or downgrade versions from a single location, improving maintainability and reducing the risk of inconsistencies.
The text was updated successfully, but these errors were encountered: