Well, the reason I suggested Ivy for dependency management was that I know that Carlo and Andy have problems with Maven in the EJB3 project. The dependency management in Maven is going to be reimplemented in Maven-2.1 - I don't like the sound of that. With this project being integrated into multiple branches of other projects dependency management is important in both directions. Like you said Ant is a bad idea implemented well, and Ivy have an almost 100% focus on dependency management and integrates with Maven repositories. I'm not married to the idea -- we can switch if we run into problems -- but the overall concept of Ivy sounds like it will solve the problems that Ant based build environments has. Well, not the overall programming/scripting in XML stuff ;) I'll setup a project on my machine and test the integration with the JBoss Maven repository, so we don't end up with multiple repositories on our disks. Thanks for your feedback, guys ! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162290#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...