Hi, We build files would need to be updated, but I suppose we could try moving one module at a time. For example, Jakarta-tomcat-site is by itself as far as dependencies. The servletapi modules would be a decent thing to move before the main Tomcat stuff, because the dependency on them is fairly clear, and we could use that move to test out our required build file changes.
It's a significant effort, I'm +0 on the whole thing. I know SVN has significant advantages, but they're not significant to me ;) I'm fine with CVS... Yoav -----Original Message----- From: Dirk-Willem van Gulik [mailto:[EMAIL PROTECTED] Sent: Friday, February 04, 2005 3:25 AM To: Tomcat Developers List; Henri Yandell Subject: Re: SVN migration? On Fri, 4 Feb 2005, Henri Yandell wrote: > I've not heard anything about it being mandatory yet, but the numbers > speak for themselves. It is not mandatory at this time. And won't be anytime soon. > So I assume at some point there'll be pressure to turn off the CVS server. There is that - as this is a volunteer ran service - and warm bodies are always in short supply. But then again - as long as there are volunteers from communities using CVS expect the kettle to not come to a boil. Ultimately -each- project needs to make their own deceisions as to what tools and techniques they use; the ASF is merely a supprint and legal backbone and container. However SVN is a bit more modern than CVS - so you may also have some internal reasons to move to SVN at some point - see the usual cvs v.s. svn google pages. Dw --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
