> -----Original Message----- > From: Thorsten Scherler [mailto:[EMAIL PROTECTED] > Sent: Saturday, 24 February 2007 7:08 PM > To: dev@forrest.apache.org > Subject: Re: [EMAIL PROTECTED]: Project forrest (in module forrest) failed > > On Fri, 2007-02-23 at 12:47 +0000, 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. Just an idea Gav... > > salu2 > -- > Thorsten Scherler thorsten.at.apache.org > Open Source Java & XML consulting, training and solutions > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.412 / Virus Database: 268.18.2/692 - Release Date: 2/18/2007
