Hi all, it seems the infrastructure guys would like all projects to move over to svn sooner rather than later, but that's a different issue.
One of the obstacles mentioned so far has been "lack of svn support in Ant". Below is a mail be Henning (reproduced with his permission) and my response to it. Expect me to (finally) propose an antlibs subproject and an svn-antlib soon 8-) Stefan > To: infrastructure > Subject: Re: Time to start prodding laggard PMCs re: Subversion? > References: <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> > From: Stefan Bodewig <[EMAIL PROTECTED]> > Date: Thu, 10 Feb 2005 09:32:18 +0100 > In-Reply-To: <[EMAIL PROTECTED]> (Henning > Schmiedehausen's message of "Thu, 10 Feb 2005 09:19:24 +0100") > Message-ID: <[EMAIL PROTECTED]> > > On Thu, 10 Feb 2005, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote: > > > 4) Some of the build tools (can speak only for the Java world here) > > don't have their SVN support on par with CVS support. Most important > > here is the ubiquitous ant which does have a number of CVS tasks but > > no out-of-the box SVN support (at least not in 1.6.2) > > With my Ant hat on, I'm surprised this is an issue. AFAIK nobody of > us has worked on a svn task yet, but the <cvs> task is just a trivial > wrapper over the command line executable as well. There are numerous > third party SVN libs that contain Ant tasks (we've been told), so we > didn't even start working on svn support to not kill off the other > efforts. > > Writing an Ant library with as much svn support as <cvs> offers for CVS > would be trivial. > > If this really seems to be a major issue, please come over to the Ant > dev list. I'm sure we could team up to code support for svn (as I > said, on par with <cvs>) within days if not hours. > > Cheers > > Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
