I'd be happy moving only those projects. Maven has had some degree of Subversion support for quite some time (available by wrapping the commandline binaries), but as to the specific functions referenced by Henning, I am not certain of the support. If it's missing, I'm willing to add it for Subversion.
On Mon, 2004-11-15 at 09:07 +0000, Eric Pugh wrote: > +1 As well, > > I think though that if we are going through the effort of moving things, > lets not move JCS and keep it under the jakarta-turbine- envelope. Either > leave it, or promote it out. > > Also, as far as other projects, I think only: > jakarta-turbine-3 > jakarta-turbine-2 > jakarta-turbine-fulcrum > > Henning, do we need to move jakarta-turbine-stratum? T2.4 doesn't use it, > and I think I can remove it from T3 as well... > > Eric > > > -----Original Message----- > > From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] > > Sent: Monday, November 15, 2004 2:23 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [vote] Conversion of CVS modules to Subversion > > > > > > Daniel Rall <[EMAIL PROTECTED]> writes: > > > > >What would y'all think about me converting our CVS modules to Subversion > > ><http://subversion.tigris.org/>? Subversion the next generation version > > >control system targeted by the ASF infrastructure team for apache.org. > > >It provides functionality very similar to CVS, but without so many of > > >its warts. > > > > Basically +1 > > > > Eric and I already discussed this a while ago. We wanted to discuss > > some structure on how to do this before rushing into conversion. > > > > One of my concerns is e.g. as maven is our build tool, to make sure > > that the report modules like maven-file-activity or > > maven-developers-activity actually work with subversion as they do > > with CVS. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
