A Gradle plugin that automates dependency version management and updates, eliminating manual searches.
refreshVersions is a Gradle plugin that automates the management of dependency versions in build configurations. It solves the problem of manually searching for and updating library versions by centralizing version definitions and providing tools to discover available updates.
Gradle users, particularly Android and Java/Kotlin developers, who want to streamline dependency management and reduce manual maintenance in their projects.
Developers choose refreshVersions for its automation capabilities, built-in dependency notations, and seamless migration tools, which save time and ensure projects stay up-to-date with minimal effort.
Life is too short to google for dependencies and versions
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The plugin provides a `refreshVersionsMigrate` task with multiple modes, such as VersionsPropertiesOnly, simplifying the transition from existing projects to centralized version management, as detailed in the migration examples.
It scans and lists available dependency updates in a centralized `versions.properties` file and versions catalog, reducing manual searches for library versions, demonstrated in the usage section.
Offers pre-defined notations for common libraries, speeding up dependency declarations and minimizing errors, referenced in the built-in dependencies notations documentation.
Supports scheduling the RefreshVersionsBot to automate update checks and notifications, enhancing maintenance efficiency without constant manual intervention.
The migration process requires selecting a mode (e.g., VersionsPropertiesOnly or VersionCatalogAndVersionProperties), adding setup steps and potential confusion for users unfamiliar with Gradle's version management options.
It's designed solely for Gradle projects, so teams using other build tools like Maven cannot leverage its features, limiting its applicability in polyglot environments.
Automated updates might introduce incompatible versions if not carefully reviewed, as the plugin prioritizes automation over manual verification, risking stability in complex dependency graphs.