+1 on that one too
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Jason van Zyl <[EMAIL PROTECTED]> wrote on 05/06/2003 10:34:11 PM:
> On Thu, 2003-06-05 at 04:04, Rafal Krzewski wrote:
> > Jason van Zyl wrote:
> >
> -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 meLet's get it documente
Big +1 from meLet's get it documented somewhere!!!
--
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 follo
> -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:
> &g
On Thu, 2003-06-05 at 04:04, Rafal Krzewski wrote:
> Jason van Zyl wrote:
>
> > Document it and it will more than likely be followed.
>
> I wish it would be so simple. Humans are lazy and forgetful, even the
> best documenation won't change that. The most common case is that some
> a person wants
Jason van Zyl wrote:
> Document it and it will more than likely be followed.
I wish it would be so simple. Humans are lazy and forgetful, even the
best documenation won't change that. The most common case is that some
a person wants to apply just a tiny little fix to a plugin.
I think that publi
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.
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 affectin
