The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Gradle buildSrcVersions Alternatives
Similar projects and alternatives to Gradle buildSrcVersions
-
-
-
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.
-
-
sixpack-java
A Java client for the Sixpack A/B testing framework https://github.com/seatgeek/sixpack
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
AboutLibraries
AboutLibraries automatically collects all dependencies and licenses of any gradle project (Kotlin MultiPlatform), and provides easy to integrate UI components for Android and Compose-jb environments
-
-
-
-
-
kotlin-libraries-playground
A playground to gain a wider and deeper knowledge of the libraries in the Kotlin ecosystem. Also the official sample for gradle refreshVersions.
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better Gradle buildSrcVersions alternative or higher similarity.
Gradle buildSrcVersions reviews and mentions
Posts with mentions or reviews of Gradle buildSrcVersions.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-19.
-
Dependency Managers Don't Manage Your Dependencies (2021)
Lately I've been using gradle with kotlin-js and a mix of npm and jvm dependencies. There's the https://splitties.github.io/refreshVersions/ plugin that I can recommend if you are using gradle (with or without kotlin-js).
It manages plugin dependencies, library dependencies, and version dependencies. It can use the new gradle version catalog or not if you prefer. On first use, you migrate your versions and it extracts these to a versions.properties (or your version catalog). Then whenever you run refreshVersions it indicates available new versions in comments in this file. It also indicates unused dependencies. Though for npms this is a bit harder. All you need to do is manually use the versions you want.
I run this frequently to stay on top of upstream changes. Few software engineers realize that the testing and integration overhead with version changes multiplies (just like with other forms of change). Libraries that you haven't updated amount to technical debt that you haven't addressed. So, the workload increases massively if you don't update for a while. Staying up to date minimizes the workload. This plugin makes that super easy.
Given that we are using kotlin-js, we have to deal with a rapidly evolving library ecosystem so we do have occasional issues that we need to work around by either downgrading or fixing some code. Whenever I can't update something, I document it in my versions.properties with a comment. Often you just have to wait for the next release or so for things to straighten out. The price of using cutting edge software.
Kotlin-js manages a yarn lock file as well. So it properly locks dependencies. Whenever you update npm dependencies, you have to run a command to upgrade the lock file. There's also a whole mess of webpack dependencies that comes along with kotlin-js.
-
Weeks of Debugging Your Build can Save Hours of Learning Gradle
{$% embed https://github.com/splitties/refreshVersions %}
-
Gradle plugin for updating dependencies?
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?
-
Easy way to migrate to Gradle's version catalog
As somebody with a deep personal hatred of TOML I recommend refreshVersions https://github.com/jmfayard/refreshVersions just a million times better and will support version catalogs soon maybe
-
How to keep all the common dependencies between multiple modules in single project gradle file?
refreshVersions, it is literally the best
- What is the best way to manage and organize build gradle dependencies?
-
How to build a GraphQL Gateway with Spring Boot and Kotlin
Note that I'm using gradle refreshVersions to make it easy to keep the project up-to-date. Therefore, the versions are not defined in the build.gradle files, they are centralized in the versions.properties file. RefreshVersions is bootstrapped like this in settings.gradle.kts:
-
Unit test your knowledge 💡
Also the official sample for gradle refreshVersions
-
A note from our sponsor - WorkOS
workos.com | 23 Apr 2024
Stats
Basic Gradle buildSrcVersions repo stats
8
1,620
8.8
3 months ago
Splitties/refreshVersions is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of Gradle buildSrcVersions is Kotlin.
Popular Comparisons
- Gradle buildSrcVersions VS logback-android
- Gradle buildSrcVersions VS WheelView-Android
- Gradle buildSrcVersions VS Guava
- Gradle buildSrcVersions VS sixpack-java
- Gradle buildSrcVersions VS deep-clean
- Gradle buildSrcVersions VS AboutLibraries
- Gradle buildSrcVersions VS ZXing
- Gradle buildSrcVersions VS anode
- Gradle buildSrcVersions VS WeakHandler
- Gradle buildSrcVersions VS PermissionHelper
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com