Sam (or whoever knows :-)), I still do not fully understand the Gump lifecycle. Here is my current understanding (please correct me where I am wrong), based on your rubix.xml (unix env) :
* You have gump checked out in /home/rubys/gump * You cd in /home/rubys/gump and you call gen.sh, which generates update and build script in /home/rubys/jakarta * You cd to /home/rubys/jakarta and you call update.sh. This checks out/update the different projects * Then you call build.sh, which generates the project builds * All logs (which will eventually go to http://jakarta.apache.org/builds/gump/latest) from gen.sh, update.sh and build.sh are in /home/rubys/Jakarta/log * The last project to be built is gump (defined in rubix.xml). As the home attribute is set to /home/rubys/gump, we find ourself in the same directory where gen.sh had initially created the work dir. At this stage I am not sure ... * It seems the "all" target that is called in build.xml recreates some of the scripts that were created by the initial gen.sh, like the build script, update script, publish script, xrefs and in addition creates some new ones : deliver (which appears to be only for unix. No windows version ?) and the naglist list. In addition it generates javadoc for Gump java classes and generates the Gump website (http://jakarta.apache.org/gump). ... and it stops here ... What is still missing : * Copy of the generated html files in /home/rubys/Jakarta/log to Jakarta.apache.org. How is it done ? * Copy of the Gump web site to Jakarta.apache.org. How is it done ? * Copy of the project build outputs (jars and doc) to Jakarta.apache.org. How is it done ? * Send emails for build failure. How is it done ? * It seems there must be a master build script on top of all these steps that ties the process together. Do you have such a script that you have put in a crontab ? Or do you perform all these steps manually every night :-) ? Thanks -Vincent -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
