Gav.... wrote: > From: Thorsten Scherler: > > Ross Gardler wrote: > > > Gump wrote: > > > > To whom it may engage... > > > > > > > > This is an automated request, but not an unsolicited one. For > > > > more information please visit http://gump.apache.org/nagged.html, > > > > and/or contact the folk at [EMAIL PROTECTED] > > > > > > As discussed previously, these gump messages are because Cocoon is not > > > building with gump right now (see > > > http://vmgump.apache.org/gump/public/forrest/forrest-test/index.html) > > > > > > We previously agreed to leave the nags in place since it would remind us > > > to keep n eye on Cocoon. > > > > > > However, with the removal of the CLI from Cocoon we cannot run on Cocoon > > > head at this time anyway. So even if Cocoon were to start building with > > > Gump again we would still fail our tests. > > > > > > So, do we turn off the gump build for a while, or should we keep the > > > nags coming? > > > > I am not sure but this two mail from gump everyday of the week are quite > > annoying (knowing there is no quick fix) but since they are annoying (a > > failure always is) they will not let us forget the open Gump issue. > > If a once a month nag was possible that would be a better solution, is that > Possible? (If they don't already exist) > > If not, we can create Jira Issues that would not let us forget.
No, i gather that it is on every run or we can stop the messages from being sent. Need to search general at gump archives, there was recent discussion. Perhaps just comment out the nag elements for "forrest" and "forrest-test". http://forrest.apache.org/gump.html We already have an issue: https://issues.apache.org/jira/browse/FOR-942 When we have our Ivy build happening, we can add that to Gump. So we wouldn't be without the integration messages for long. Not sure whether it is better for Gump's history to have new "project" names or re-use the old ones. If no-one beats me to it, i will work on this soon. -David
