On Tue, 26 Mar 2002 22:04, Sam Ruby wrote: > > first steps to move nagging into project descriptors > > In general, my thoughts have always been that notification should be > orthogonal to project definition.
I sorta agree but for pragmatic reasons I would like to see it put in the module descriptors so that the responsibility for maintaining em can be pushed out to the users. It would make it much easier for users to add specific nags ie I would like to be notified when any of the projects I am working on start to use deprecated APIs so I could add a nag for that, similarly I would like to add nags for checkstyle violations for any of the projects I am in etc. However moving this into the central gump repository would make it harder for me to add these nags (if I wasn't a committer that is) and harder to remove them after no longer relevent. BTW: If anyone is taking feature requests for nags atm heres two things I would love to see ... * summary nags; ie send one mail with a list of all failuress in a set of projects and URL pointers to the relevent web-pages * wildcard nags; ie I want nags for all modules that match pattern "jakarta-avalon.*" or maybe all projects that match pattern "(jakarta-avalon.*|excalibur-*)" -- Cheers, Pete "Invincibility is in oneself, vulnerability in the opponent." -- Sun Tzu -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
