Berin Loritsch wrote: > > Gump is an automated build tool designed for early warning when an API > changes. It always grabs the full CVS version, builds that project, > and uses the built jar for building anything that depends on it.
Gump is an automated build tool. Early warning whan an API changes is a tangible benefit. Such benefits accrue when Gump is directed to always grab the full CVS version, but gump can be told to use installed packages, or jars in cvs. I personally believe that Gump is useful for anybody who trys to coordinate the building of several cvs trees, and would be glad to answer questions and provide support for anyone interested in doing this. > Therefore, if Excalibur requires JUnitPerf (which I have been wanting > to add tests for but never got around to it), we need to update GUMP's > profile to include JUnitPerf. "we" ;-) > I have already sent an email to [EMAIL PROTECTED], and > hopefully it has been updated. > > That is all that needs to be done. The e-mail could have provided a bit more information, such as where the jar could be found (it isn't in excalibur). In the ideal world, it would have come in the form of a patch. (hint, hint) To see examples of gump project definitions, you can go here: http://cvs.apache.org/viewcvs/jakarta-alexandria/proposal/gump/project/ Gump (configured to use the latest CVS versions) runs every six hours on various machines. Depending on when dependency changes are made, I often can see the impact and make the fix before you get a nag message. More information on Gump, background on why it was created, and documentation of the descriptions, and much more can be found here: http://jakarta.apache.org/gump/ - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
