At one time, my 3rd-party repo almost hit 1GB (committed to SVN). ANT script becoming more and more complicated. Running unit-test? running integration-test? S

At one time, my 3rd-party repo almost hit 1GB (committed to SVN). ANT script becoming more and more complicated. Running unit-test? running integration-test? SVN hooks? extra work, lots of... Extra JARs (e.g.: Log4J 1.1 and Log4J 1.4) sometimes got included to the WAR or the deliverable output package because multiple projects refer to the same 3rd-party repo but individual project decided to use different versions of the library. To his of its own, we decided not to move to Maven but instead opted for Ant+Ivy. Thing is, Maven or Ivy is becoming a norm because _many_ people like me decided that it's the better way to go and we are ready to give up some of the things we had before. Our build is 100% reproducible _and_ correct vs 100% reproducible _but_ maybe 90% correct. One of the advantage of Maven (in Eclipse via m2clipse) is the less time it requires to setup 3rd-party JavaDoc _and_ the actual Java source code (assuming the author upload the Java source code to the M2 Repo). I can easily navigate to the source code because m2clipse will download it for me for free. Do that with ANT + Eclipse and I guarantee you that you will burn some time to set things up _AND_ it won't necessarily be cross-platform (often it won't work well across 2 different machines with the same OS anyway if someone decided to mess up with the actual .classpath). >And what happens if you have an Internet connection but some high-target repo gets rooted and a major Java .jar gets replaced with a version containing an exploit? Examples? Frequency? You can say the same with FreeBSD packaging, Debian and Ubuntu apt-get repo, or any similar systems. Again, most of us are thankful that Maven (and IDE integration) exist. To bad you're not.