> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 10 June 2003 09:42 > To: Maven Developers List > Subject: Re: Committers let's agree on how we make changes to a plugin > > Big +1 from me....Let's get it documented somewhere!!!
Done here: http://nagoya.apache.org/wiki/apachewiki.cgi?Maven/PluginModificationGui delines and linked in the "development process" page. -Vincent > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ > Work: http://www.multitask.com.au > > > "Vincent Massol" <[EMAIL PROTECTED]> wrote on 04/06/2003 10:49:15 PM: > > > 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? > > > > Thanks > > -Vincent > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
