> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 17 November 2003 00:03 > To: 'Maven Developers List' > Subject: RE: Announcement plugin > > > - Is it a problem of catalog, i.e. finding what a plugin does > > or what plugin matches something I'm trying to achieve as a user? > > Yes
this can be solved and is a more general problem. > > > - Is it a problem of overhead due to a plugin (project.xml, > > lifecycle, JIRA project)? > > yes > > > - Is it a problem of users having to install more plugins? > > Yes this can be solved and is a more general problem. > > And there is also an additional runtime hit for additional plugins. We should address this. Why cannot it be a fixed overhead, like a hashmap lookup cost? > > But really, I think the main thing is keeping similar tasks together, > which > encompasses all of these. It needs to be a balance between this and > unreasonably coupling everything. > > Right now, announcement uses only changes.xml and project.xml, which > indiciates to me it belongs in the changes plugin. It is only done at > release time, which means it could also be part of the release plugin - > although I think it should call out to the changes plugin to ask for an > announcement to be generated. Why not? I am not against it. I still think it is cleaner to separate it. What do others think? Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
