News for hackers. Stuff that matters.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by guelo on Tuesday January 02, 2018 @07:33PM (#16057301)
I think it happens because maven has poor documentation, a ton of unexplained "convention over configuration", and very strong poorly explained opinions about how you must structure your project. Basically it's a ton of inflexible magic. Also, the attitude in the maven community that people that want to deviate from the god-given-way are two year old children.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by hugi on Wednesday January 03, 2018 @07:04AM (#16060286)
This is basically the exact opposite of my experience with Maven. The documentation feels very clear and good to me and I've always found answers to my questions. I don't recall ever encountering "unexplained inflexible magic".
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by harlanji on Wednesday January 03, 2018 @10:59AM (#16062042)
In around 2008 I co-wrote a set of maven javascript mojos (before NodeJS), incl QUnit test integration et all. I collaborated with another fellow on the other side of the world. Documentation was stellar. IIRC, to extend, even the upgrade from M2 to M3 didn't affect most community mojos.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by lmm on Wednesday January 03, 2018 @04:36AM (#16059668)
Maven's documentation is great, and the project structure is well explained. Inflexible yes, magic no.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by pjmlp on Wednesday January 03, 2018 @01:36AM (#16059008)
The Maven manual is quite good, and there are plenty of books available for those that bother to sponsor development.