Stefan Bodewig wrote: > > I've just had a quick look over Sam's script, but I think he is making > it too easy for the projects 8-). The stuff the script does in gather > should be done by Ant inside the build.xml of the specific projects > IMHO.
I have no problem with a little social engineering. ;-) > After that, pretty much all that needed to be specified in a gump > descriptor was a directory that contains all the tars and zips and > md5s and rpms and whatever that should be posted as nightly builds. Perhaps I should also show what is run "on the other side". One thing that is notable is that all of jakarta-avalon-* projects are placed into a single directory. (See attached file: post_to_website) What you are witnessing (and hopefully will participate in) is how gump has evolved to date. First I hand coded scripts. Patterns formed. Then these patterns were automated. Most of the effort is in getting the data definitions right. If you can help there, I will fill in whatever gaps are required with the scripts. - Sam Ruby
post_to_website
Description: Binary data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
