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/scm plugin.jelly project.xml > > > 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, 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-SCM which does all the translation to specific > > versioning systems. > > > > Also, all the release management stuff I added doesn't > belong in there > > in the long run. > > > > - Brett > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
