Understanding Gradle #10 – Dependency Version Conflicts

preview_player
Показать описание
What are dependency version conflicts? Why do I have to deal with them?

▶️ 0:00 Dependency Version Conflicts
▶️ 0:26 Example: Producing a conflict
▶️ 2:25 Effects of Gradle's default resolution behavior
▶️ 4:20 Different classpaths can have different resolution results
▶️ 5:05 Consistent resolution
▶️ 7:35 Shared applicationRuntimeClasspath
▶️ 10:16 Strict version constraints
▶️ 10:39 Summary

Related Videos:

Further Readings:
Рекомендации по теме
Комментарии
Автор

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

ethanhunt
Автор

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?

henninghoefer
Автор

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

AliaksandrSmirnou
Автор

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?

TomKoptel
Автор

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

caffeinejavacode