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).<p>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).<p>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.<p>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.<p>I deal with the lack of a lock file by using maven parent poms, sonatype, enforcer plugins, and version plugins.
Next-In-Thread:<p>---<p><pre><code> We see Ivy as a widely used component.
We use archiving some components to
recalibrate our focus. I don't think
that we want to archive Ivy in the near
future. Instead we try to push Ivy.
If you want to help with Ivy, you're welcome.
"It's already a challenge to stick with
Ivy build system itself given the lack of
fixes/releases/responses." What are the
problems you think are resolved with new
Ivy releases?
Jan
</code></pre>
---
Doesn't sbt still use Ivy under the covers? I know Gradle used to but maybe not anymore. In any event, Ant is still an active project and Ivy is it's dep system.
A project I used to work on (opticks.org) used Ivy. At the time, Ivy was the best solution we could find for C++ dependency management.<p>Are there any good cross-platform alternatives for C++ dependency management?
Irrelevant aside: my eyes! I was astounded to see plain text twisted up so badly. It literally made my eyes water. Was that some artful/ironic attempt to reproduce ink-bleeding typewritten pages? *View/Page Style/No Style" was the only way I could tolerate this.