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
Gradle Version Catalogs allow developers to mange dependencies across modules from a single filegradle/libs.versions.toml, which contains 4 sections:
[versions] declares what versions are used by the dependencies
[libraries] declares our libraries/dependencies
[bundles] allows defining groups of dependencies that are commonly used together
[plugins] declares our plugins
This allows us to centralize the dependencies declared across modules and submodules. We can replace Dependencies, Plugins and Versions from the buildSrc module with a single project level gradle/lib.versions.toml file 🙇🏻
Why
Gradle Version Catalogs allow developers to mange dependencies across modules from a single file
gradle/libs.versions.toml
, which contains 4 sections:[versions]
declares what versions are used by the dependencies[libraries]
declares our libraries/dependencies[bundles]
allows defining groups of dependencies that are commonly used together[plugins]
declares our pluginsThis allows us to centralize the dependencies declared across modules and submodules. We can replace
Dependencies
,Plugins
andVersions
from thebuildSrc
module with a single project levelgradle/lib.versions.toml
file 🙇🏻References
Who Benefits?
Developers
The text was updated successfully, but these errors were encountered: