3 ms·
Correctness is the number 1 priority, and maven is simply not always doing what it should, unless you do a clean build. I am absolutely not bothered by XML and
by kaba0 2y ago
Correctness is the number 1 priority, and maven is simply not always doing what it should, unless you do a clean build.
I am absolutely not bothered by XML and alia (btw, there are maven frontends in json/yaml, etc for those who are), and throwing out valid criticism over some straw man is not really productive.
- nophunphil 2y agoI’m still learning about the tools and their pros and cons. Can you provide an example of a case where Maven would not do what it should? Are there particular bug reports or bug reproduction repos that you’ve seen? Context: I worked on a Spring app many years ago and am picking Java back up.
- kaba0 2y agoHere is a case: https://stackoverflow.com/a/4662537 https://stackoverflow.com/a/4662537 But I have run into issues with multi-module projects and the like, and it can be very frustrating to realize that you are trying out some corrupt version. Nonetheless, maven is also a cool and stable tool, but you are better off adding a clean step from time to time.
- pjmlp 2y agoAs if Gradle was any better in "correctness" given without its daemon, it is a slower Ant for folks with XML allergy.