Try creating a Java multi-dependency project without Maven and just manually adding the jars. It's super annoying as nested dependencies will arise and sometimes conflicts. :P

But...why?

But... Why?

But... Why?

No more "but"s for today, sorry 😀

Well, Maven to Java is like npm to Node.js. Many people would easily be discouraged if Node.js wasn't distributed along with npm.
Guess why Java seems like "masochism" to community? Because developers of legacy software were not bought by Maven's charm and kept on producing in-house dependency injection strategies. Pfft, it's in my plain sight: large PLM, that I customize, struggles with this, it doesn't put every class in named package, instead they use "advantages" of default package, which only turn out to be disadvantageous. Staff was known to blame Maven for some unknown security holes and told to use Ant... Wait, really? - I ask.

I mean ant is basically manual

@yellow-dog It was before ivy.

@Makenshi So you can test your limits and learn how a language and a system are truly built. This was pretty common back at university when we were doing Programming 201.

Always deconstruct everything before attempting to use fancy tools. After all, the word 'university' focuses on the 'universal'.. we must apply that which is fundamental. It's important to know that if you want to learn something, you need to start with its very core.

@vintprox ButtIndexOutOfBoundsException