can still be added to the current SCM one until it
> does materialise?
>
>
>
> > -Original Message-
> > From: Dion Gillard [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, 27 May 2004 9:44 AM
> > To: Maven Developers List
> > Subject: Re: cvs c
Why? Surely the stuff can still be added to the current SCM one until it
does materialise?
> -Original Message-
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 27 May 2004 9:44 AM
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/s
No worries.
I'll create a private cvs plugin in the meantime.
On Thu, 27 May 2004 09:22:55 +1000, Brett Porter
<[EMAIL PROTECTED]> wrote:
>
> > However, after looking at the scm plugin, I'm more convinced
> > we need a cvs plugin separately, and use the scm plugin to
> > bring it all together, r
> However, after looking at the scm plugin, I'm more convinced
> we need a cvs plugin separately, and use the scm plugin to
> bring it all together, rather than all the goals being in the
> one plugin.
>
Don't get carried away doing that. The next incarnation of the scm plugin
can use Maven-SC
Sure, I'll do it later today.
However, after looking at the scm plugin, I'm more convinced we need a
cvs plugin separately, and use the scm plugin to bring it all
together, rather than all the goals being in the one plugin.
On Thu, 27 May 2004 08:52:51 +1000, Brett Porter
<[EMAIL PROTECTED]> wrot
changes.xml?
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 27 May 2004 2:11 AM
> To: [EMAIL PROTECTED]
> Subject: cvs commit: maven-plugins/scm plugin.jelly project.xml
>
>
> dion2004/05/26 09:10:52
>
> Modified:scm/xdocs prope
