All my previous comments are still valid, maven is not just the automatic dependency download or the transitive dependencies, but let’s focus in these two aspects.
- Ivy uses the maven 1 repository at ibiblio to get the jars, which is mantained and administered by the maven project.
- The ivy repository only hosts metadata about 55 artifacts, while the maven 2 repo has metadata for more than 4000 projects (I’ve excluded poms smaller than 200 bytes)
The main problems we have at maven is missing or incorrect metadata, so if there’s any Ivy user reading this I’d like to know what’s the point of using it when only a few projects have metadata. And while in maven is a collective open effort, seems that it’s not like that with Ivy.
If I’d like to use ant for my build (never again if I can avoid it, specially since we have the antrun plugin), I’d choose the m2 ant tasks, that as a side effect allows you to also run maven, providing a good migration path.