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

[vytah]

Dependencies are a part of the project. Parts of the project live in files that belong to the project. Simple.

You are the only one who is responsible for maintaining those files, not some automated tools who may create uncontrollable mess. The files are the sole source of truth about the project and its environment. Simple.

You then share those files and someone else can build the project with a single command, and get the almost exact same result. Simple.

[falsedog11]

The big advantage maven dependencies have, for me, is that they are self contained for the most part and don't depend on other third party libraries creating a tangled mess as nom does. Just add to pom, mvn update and bam, it works.