Dunno whether this helps or not, but I first wrote our entire build process in Perl. It handled retrieval from VSS, labeling VSS, checking in new version stamped code, compilation, resource copying, EJB'ing, packaging client classes together into jars, signing jars, RMIC'ing using standard Java RMI and Weblogic RMI, backing up source, uploading to a test server and finally deploying the test server.
I switched to Ant because I was tired of developers asking me to implement new features in the Perl scripts. By using a Java based build tool, our Java developers could no longer claim they didn't know how to modify or use the build process. -----Original Message----- From: Chappell, Simon P [mailto:[EMAIL PROTECTED]] Sent: Monday, April 01, 2002 10:39 AM To: Ant User mailing list (E-mail) Subject: Research question I'm writing a proposal for using ant internally as part of our standard build process and I am having difficulty finding information on the alternatives to ant. I have tried many different searches on the mighty Google, but with less than wonderful success. The few that I found seem to mostly have withered and died and a few even suggest switching to ant! :-) Can folks on this list point me at a few other tools that I can list in my document. Specifically, I am looking for build tools that are designed for Java systems (hence "make" doesn't make the cut). Simon ----------------------------------------------------------------- Simon P. Chappell [EMAIL PROTECTED] Java Programming Specialist www.landsend.com Lands' End, Inc. (608) 935-4526 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
