> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 04 June 2003 22:46 > To: Maven Developers List > Subject: Re: Committers let's agree on how we make changes to a plugin > > On Wed, 2003-06-04 at 08:49, Vincent Massol wrote: > > Hi, > > > > What do you think about the following process for making changes to a > > plugin (and for accepting patches): > > > > 1/ Update xdocs/changes.xml (create it if it does not exist) and > > describe the change > > 2/ Update the goals.xml/properties.xml and more generally the plugin > > documentation if changes affecting users have been made > > 3/ Ensure that the version in plugin.xml is a SNAPSHOT version (i.e. not > > delivered). Unless you're making a release of the plugin. > > 4/ Make sure the <version> section of project.xml is up to date > > > > Almost everytime I make changes to a plugin I find that these simple > > rules are not followed (Note: I know dIon is also careful about them). > > > > What do you think? > > +1 > > Document it and it will more than likely be followed.
I have started here: http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/PluginModificationGui delines I have also linked this page from the Development process page of the maven web site (but I haven't republished it yet). Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
