Understanding Gradle #10 – Dependency Version Conflicts

Hi Jendri 👋 Very nice and thorough explanation of consistency issue between different class paths. I was thinking about introducing similar concept as shared applicationRuntimeClasspath on Android project. Though it is not clear for me i it can be achieved in the Android Gradle Plug-in world. Any advice on how to? Maybe link to gist or some sample project that tried to solve the problem in the past?

What about
dependency tree conflict (Spring Boot Gradle)
if on the third level Gradle can't find dependecy

Hi, thanks for your efforts. I am learning a lot from your videos. I stumbled upon your channel in search of the solution for this error in my android project, "Problem: Inconsistencies in the existing project dependencies found. Version incompatibility between: - com.google.android.material:material:1.8.0@aar and: - androidx.appcompat:appcompat:1.6.0@aar With the dependency: - androidx.annotation:*:1.1.0 versus: - androidx.annotation:*:2.0.0". I still can't solve it, would please help me solve this problem?

Hi!
thanks a lot for your videos!
can you suggest good book about gradle where I can read about all this features

Admittedly, I had to watch this a second time to understand how it works – every module depends on the application module, but only in the new applicationRuntimeClasspath configuration, right?

But that got me thinking – what happens, if a library is used in multiple apps? In that case, that library would depend on all apps it's used in (again, only in the special configuration), but couldn't that introduce conflicts again? Because the different apps again don't know about each other?

Such an underrated channel.. Amazing work..Subbed!