I was a long time user many many years ago of Ivy. I will say Ivy is one of the most sophisticated dependency management libraries/tools. It has things I have y

I was a long time user many many years ago of Ivy. I will say Ivy is one of the most sophisticated dependency management libraries/tools. It has things I have yet to see other dependency managers do (and probably should not do anyway). The flexibility was sort of good for our enterprise code base that was still using Ant but over all it was just way too complicated (this was in part because it was not integrated with any particularly build system at the time ~ 8 or so years ago). I have come to the conclusion that with proper parent poms and enforcer plugins (particularly dependency convergence) you can generally get Maven to do a fairly good job. The only thing I can't decide is if Maven (and Ivy for that matter) should have lock files. I have some ambivalence to lock files (ie a file that gets auto generated and that you check in). Bundler and cargo do it as well as a netflix gradle plugin. I deal with the lack of a lock file by using maven parent poms, sonatype, enforcer plugins, and version plugins.