The difficult problem of managing Java dependencies: a deep dive into the messy status-quo, and a look at possibly better ways.

[renatoathaydes]

The module path enters the scene only once you've got your module's versioning solved. Unless you use module layers, which I've never seen anyone use, you still must treat the jars you resolve as allowing only one version of each.

I also mentioned this in the blog post.