Colin Sampaleanu claims that Ivy is everything Maven should have/could have been 2.5 years ago.
While I understand where he is coming from, and I think Ivy is a nice piece of software, I have to stand up for Maven again.
Even though, I know that I will get bashed for it.
Handling dependencies is a very nice thing. And, having transitive closures on those dependencies is going to be great to have in m2.
However, this isn’t the only part of a build, nor of Maven. Maven is my build container. It takes care of so much that I don’t have to worry about, and I haven’t had to get deep into Jelly code, like others have expressed.
m2 is not going to come rushing out there, and you can’t blame the authors! They are going to learn from their mistakes, and my guess is that when m2 finally does rear its head, we will be impressed.
Also, in related news, Vincent Massol is writing a Maven book for O’Reilly.
disclaimer: just because I have had a good experience with Maven does not mean that I am trying to ram it down YOUR throats, and I understand if you don’t chose to use it :)