4 ms·
I feel that transitive dependency is convenient, but that's what makes your application fat. Moreover, many of those transitive dependencies aren't actually ne
by vbezhenar 2y ago
I feel that transitive dependency is convenient, but that's what makes your application fat.
Moreover, many of those transitive dependencies aren't actually needed (they might be needed for some obscure feature that you don't use). Good libraries might declare those dependencies as optional, but not always.
And almost all dependency conflicts arise from multi-level transitive dependency problems.
May be it's better to just instruct user which transitive dependencies he has to install and let him do the job.
I, myself, miss dumb simple java build tool which would to the very minimum of job. I'm happy to assist it when necessary. Maven is nightmare and Gradle is hell of a nightmare. I don't need that complexity for my projects but I have to pay the price. I often think to downgrade to Makefile or shell script.
- npstr 2y agoDo the downgrade. And please report back how you like it.
- znpy 2y ago> I, myself, miss dumb simple java build tool which would to the very minimum of job. I did that in ~2007 with apache ant. I barely understood the tool (have mercy, I was 15 at the time) and had cobbled up a very basic build.xml file. It did build and it did assemble a runnable jar file, given a classpath containing the dependency jars (i wasn't using many, like 1 or 2). I still had to download the jars and manually place them in a sub-directory. if you want a build tool that can be very dumb I'd say that ant is what you need. It can be as dumb or as smart as you want it to be.
- Osiris-Team 2y agoYeah I wish I could say build tools are simple. 1JPM was until I had to deal with transitive dependencies. The recursion going on there broke my mind quite a bit.