Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
I need a Gradle plugin for managing version upgrades for dependencies. I used refreshVersions; however, I don't like how those dependencies end up in multiple files, e.g., versions.properties vs lib.versions.toml. I want something simpler. So, what do you prefer?
This can tell you about new versions https://github.com/ben-manes/gradle-versions-plugin
This can also auto-update the TOML, afaik using the plugin above internally https://github.com/littlerobots/version-catalog-update-plugin
My team uses the Gradle Use Latest Versions Plugin. It'll update versions in a few possible locations. We keep most of our version numbers in gradle.properties, except for a few plugins where we use the "new" plugins syntax (which doesn't support pulling values from gradle.properties).
Related posts
- Weeks of Debugging Your Build can Save Hours of Learning Gradle
- Easy way to migrate to Gradle's version catalog
- How to keep all the common dependencies between multiple modules in single project gradle file?
- What is the best way to manage and organize build gradle dependencies?
- Dependency Managers Don't Manage Your Dependencies (2021)