Surviving Dependency Hell with Maven by Robert Scholte and Ray Tsang

Dependency conflicts come in many different forms and have different impacts on your applications. This presentation examines common causes of a dependency conflict, how you can mitigate it as a library developer, and how end users can resolve it. Java Champions Ray Tsang and Robert Scholte will share their knowledge, Ray (developers advocate for Google) from the user perspective and Robert (chairman Apache Maven) from the Maven perspective. Join this session to see common issues Ray has observed from working with customers, and Robert’s advise on how to detect issues early. It also covers what Google has been documenting in terms of best practices and what tools it has created to help, based on its learnings.

[skrrytch]

This was really an eye opener for me. Thank you. Nevertheless ... I think you didn't mention how to fix split package problems: When using spring boot I have many dependencies to versions of "jakarta dependencies" (e.g. jakarta.activation-api) which duplicates javax.activation-api from other libraries. They both have differen group ids, artifact id, versions and classes hashes ...

[debkr]

Can't we just exclude `guava-jdk5` to resolve the issue?

[interrogationwatch]

The problem is more or less the attitude of open source projects to put in a s*hit ton of dependencies for the sake of „hey there is a library. we use it“
How many times you see os projects using apache commons io, … for just one method. That brings the cost of having a ton of CVE‘s i side your project and spills up your processing and introduces a dependency hell.
It is such a shame for „modern“ development.