gradle-versions-plugin VS Dagger2

This can tell you about new versions https://github.com/ben-manes/gradle-versions-plugin

In one of my larger projects I use https://github.com/ben-manes/gradle-versions-plugin to update dependencies every couple of weeks. I manually go through each available update, and now I have to check every androidx update to see if it's one of these special versions. On top of that, if it is, I have to go manually check if there was an update to the version that I'm on but beneath the special version.

In the meantime you can use the gradle-versions-plugin or one of its extensions. I wrote it a decade ago and naively hoped they would have offered something built-in and better by now. Maybe they finally will if the above moved forward.

https://github.com/ben-manes/gradle-versions-plugin is my go to plugin for updating and maintaining plugin versions (also allows you to update to stable only versions of dependencies once you setup some custom gradle methods.(note jitpack has bad meta data so you'll have to exclude this lib from that repo)

I like https://github.com/ben-manes/gradle-versions-plugin but there are others out there that are more up to date and provide more features. I only used it for dependency report generation. I'm going to play around with this and others more in the near future and see what one(s) I like.

Creating your own pre compiled script plugins for tidying up your build.gradle config and give an example showcasing config for the popular the popular versions gradle plugin

There used to be a thing called "releasable references" which was that. It was removed, though: https://github.com/google/dagger/issues/1117

As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.

At Reddit, we use Dagger 2 for handling dependency injection (DI) in our Android application. As we’ve scaled the application over the years, we’ve accrued a bit of technical debt in how we have approached this problem.

Confusing. I initially thought someone ported the Dagger DI framework to Python: https://dagger.dev/

I'm currently using Dagger and Anvil for my DI needs. It's been working really well, especially around what Anvil permits in terms of multibindings defined on the type declaration rather than in a module. For example:

Great job, I have been waiting for this feature/fix for a long time https://github.com/google/dagger/issues/2328

Dagger