modern-java-practices

The maven pom.xml contains a lot more than what would be in cargo.toml. How much extra config or shell scripts would cargo have to have to add code coverage, findbug tools (that do things like linting and pattern matching to detect common coding errors)? How much extra is needed to add a unit testing mechanism, an integration testing mechanism, a dependency checker (e.g., checking if you're not using a duplicate transitive that is pulling in different versions that might clash)? The only thing comparable to cargo.toml is these 40-ish lines[1], which you pay double for the xml tax. The rest are things that are adding value, but could be removed (tho i would say it's adding a lot more value than it's costing you lines of code). [1]https://github.com/binkley/modern-java-practices/blob/master...

Looks to be a lot of useful experience summarised here. I've just skimmed parts so far, but will come back and read more as time allows. > https://github.com/binkley/modern-java-practices#keep-your-b... It boggles my mind that in this day in age, Maven still recompiles everything if you touch anything. The problem of figuring out what files need to be built and building only them was solved for C in I think the late 70s (makedepend). I don't know if Gradle is better in this respect. (It certainly can't be worse.)