3 ms·
I am not very experienced in using Maven, but the biggest problem I have with it is, that it is hard to tell (at least for my level of experience) from where de
by chopin 13y ago
I am not very experienced in using Maven, but the biggest problem I have with it is, that it is hard to tell (at least for my level of experience) from where dependencies are pulled. Is it my local mirror, is it something on a central nexus in the company or is it totally from outside?
Build reproducibility, which the author mentions is another issue. When I scrub the local mirror, the outcome can be completely different. Previously builds where working fine, when I scrub, everything breaks. This is mainly due to non-local dependencies which had been cached locally, but not replaced by most recent versions.
Another suspicion I have is that most build scripts are slapped together by googling until it works. Which of course is prone to being fragile (not to mention legal issues because it is opaque from where all stuff is pulled).
- fs111 13y agoNever, ever, ever add any repositories to your pom.xml. Never. Have one central repo (nexus, artifactory, whatever) for your organization and make it a mirror of all others via settings.xml, not in the pom. This adds a lot to build stability and reproducibility.