> -----Original Message-----
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]]
> Sent: 02 April 2002 14:09
> To: [EMAIL PROTECTED]
> Subject: Re: cvs commit: jakarta-alexandria/proposal/gump naglist
>
> On 29 Mar 2002, <[EMAIL PROTECTED]> wrote:
>
> > If all goes well, tonight's nags will come from the naglist that
> > Stefan produced...
>
> woohoo
>
> Some thoughts on how I intend to extend it (but it may take a while as
> my initial itch has gone away):
>
> * Provide defaults for a module. It is rather cumbersome to add nag
> elements for all the projects in commons-sandbox - and they all even
> look the same.
>
> * Ability to define additional naglist entries from the workspace.
>
> * Ability to define naglist entries for groups of projects from the
> workspace (Peter's request) - maybe collecting those project names as
> regexps or glob patterns.
>
> * Finer control over the nag mails sent. Right now it is an "send to
> all lists or don't send anything" approach. I'd like to define in the
> workspace that nag mails should only be sent to a given subset of
> projects.
>
> Any other things for the wish list?
1/ Make the pieces tie together. For the moment once you've installed
Gump you're still half the way and you need to bring the pieces together
:
* execution of gen.bat
* execution of update.bat
* execution of build.bat
* run the nag.pl script to send emails
* run the deliver script to copy files to server
* use crontab to loop
2/ Make it work on Windows :-). I can test it on my machine if you wish
:-). I don't have much cycles for the coming 2 weeks to write the
patches myself (and finish understanding gump) but after that I should
be able to help.
Thanks
-Vincent
>
> Stefan
>
> --
> To unsubscribe, e-mail: <mailto:alexandria-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:alexandria-dev-
> [EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
