Some updates to your presented information

[cstamas]

Howdy,

This blog https://blog.ltgt.net/maven-is-broken-by-design/ was written in 2013 (11 years ago), and many (not all) statements from it are simply not true anymore in Maven (3.9.6 is latest), especially the "Repositories are all checked for all dependencies" (which, AFAIR was in fact never true) as since 3.9.0 there is RRF https://maven.apache.org/resolver/remote-repository-filtering.html

Shrinkwrap OTOH moved to MIMA https://github.com/maveniverse/mima and new upcoming CLI is https://github.com/maveniverse/toolbox

Have some fun trying those out! Have a nice day :smile:

[cstamas]

Moreover, Resolver got "open scope" system (example how are today mvn3 and mvn4 that has some new dependenct scopes introduced): https://github.com/apache/maven/tree/691e3780e6cd86f7ce2e3ed51ecd016acc984368/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/scopes

The "path" (where dependency goes, classpath or module path) is new upcoming Maven4 feature: https://github.com/apache/maven/blob/master/api/maven-api-core/src/main/java/org/apache/maven/api/Type.java

As IMO that is not part of coordinate (you can have a JAR used as CP but also as MP dependency, is up to consumer).

[bowbahdoe]

I got rid of the reference to repos being checked for all dependencies.

As you can tell maybe from the README sorta trailing off at the end there, I didn't expect many (any?) people to find this beyond those I shared it with directly. Though I guess it was inevitable once i shared the CLI repo.

I'm sure i'll have questions for you when i get back around to this to fix the outstanding bugs, now that I got your attention.

[cstamas]

About finding this: you blogged about it, and I am present on reddit as well (but I missed the post originally, just found it recently).

Sure, feel free to ask!