With most automated builds written in perl it is possible to break the build up into several portions. (e.g. Build, Package, Ship, Deploy) This leads me to ask the following Newbie questions: 1. Assuming that I have a principal build.xml file that performs the build and even creates the directory structure that I will copy/distribute internally. How would I call a distribution.xml file that would contain the move/copy functions? 2. How would I pass init variables from one .xml to the next "called" .xml file? 3. The log file that I'm generating via ant -logfile function is not actually closed out by the time I'm ready to distribute when I use the "all in one" approach with my build.xml file. If I can use a build.xml file that calls a compile.xml and then a distribute.xml file, I would be able to include the completed logfile with my distribution. Currently, I am using a cmd shell in WinNT to do this, but would like to keep it fairly platform inspecific. Any pointers would be helpful.. Thanks! David -----Original Message----- From: Hayes, Peter [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 03, 2001 2:22 PM To: '[EMAIL PROTECTED]' Subject: -projecthelp Hey, Is there anyway to suppress the Subtargets when doing ant -projecthelp. We use a lot of intermediate subtargets that make the help less than useful when it scrolls off the screen. Thanks.
