That would be a way to actually start with a 4.0 branch fork which might be more manageable due to fewer changes to merge between the cvs and svn repositories.
Can we get the jboss-4.0.x and jboss-head contents moved into svn Damon? -----Original Message----- From: Adrian Brock Sent: Saturday, February 11, 2006 3:48 AM To: Scott M Stark Cc: jboss-development@lists.sourceforge.net; QA Subject: RE: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMavencliff On Sat, 2006-02-11 at 04:33, Adrian Brock wrote: > On Fri, 2006-02-10 at 13:28, Scott M Stark wrote: > > Let's do that. Do you want to couple this to maven? It would help Ruel I > > suppose. > > We may as well go "Big Bang!". :-) Speaking of Big Bang. It might be idea to convert to subversion at the same time. Given we want to refactor the project structures to native Maven we could: 1) Import CVS into SVN 2) Use SVN rename to rework the project structure 3) Keep the history attached to those files! http://weblogs.java.net/blog/joshy/archive/2005/03/subversion_rena.html -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
