On Sep 19, 2008, at 9:03 AM, Joe Attardi wrote: > Marden Marshall wrote: >> At this stage the config server team have only introduced three >> RPM's, dnsjava, commons-net and jain-sip, all of which are >> available from sipXcommons. Before they go any further down this >> path, they should seriously rethink this new strategy. > What about Apache Ivy? > > It's an Ant subproject that takes the only good thing about Maven > (dependency management) and works hand in hand with Ant to download > dependent jars. That's about all I know about it at present, but > maybe it's worth looking into. >
Both Damian and I have at different times explored the possibility of using Maven for our dependency management. Personally I really liked the elegance and control that it provides. The two problems that I had with it were the need for deterministic repositories and the difficulty in retrofitting existing projects. It looks like Ivy might be able to address the later issue. Assuming that is true, then the only way that I would be willing to embrace it would be if we were able to maintain our own maven repository. I don't want to have to rely on third party repositories that might or might not we available when I need to get a release out the door. I've set up repositories before. It's not difficult and the overhead in maintaining one would be no greater than maintaining the jar files in subversion as we currently do. We would just need Nortel's commitment and support. -Mardy _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
