[jboss-remoting-commits] JBoss Remoting SVN: r4271 - remoting2/branches/2.x/docs/guide/en.

[jboss-remoting-commits at lists.jboss.org]

Author: ron.sigal at jboss.com
Date: 2008-06-08 19:25:36 -0400 (Sun, 08 Jun 2008)
New Revision: 4271

Modified:
   remoting2/branches/2.x/docs/guide/en/chap14.xml
Log:
JBREM-987: Updated cvs to svn.

Modified: remoting2/branches/2.x/docs/guide/en/chap14.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap14.xml	2008-06-08 22:43:24 UTC (rev 4270)
+++ remoting2/branches/2.x/docs/guide/en/chap14.xml	2008-06-08 23:25:36 UTC (rev 4271)
@@ -1,28 +1,40 @@
   <chapter>
     <title>Getting the JBossRemoting source and building</title>
 
-    <para>The JBossRemoting source code resides in the JBoss CVS repository
-    under the CVS module JBossRemoting. To check out the source using the
+    <para>The JBossRemoting source code resides in the JBoss SVN repository. The
+    tagged versions are found in
+    https://svn.jboss.org/repos/jbossremoting/remoting2/tags, and the working
+    branches are found in
+    https://svn.jboss.org/repos/jbossremoting/remoting2/branches.</para>
+    
+    <para>To check out the source for version 2.4.0.GA using the
     anonymous account, use the following command:</para>
 
-    <programlisting>cvs -d:pserver:anonymous at anoncvs.forge.jboss.com:/cvsroot/jboss checkout JBossRemoting</programlisting>
+    <programlisting> svn checkout http://anonsvn.jboss.org/repos/jbossremoting/remoting2/tags/2.4.0-GA.</programlisting>
 
-    <para>To check out the source using a committer user id, use the
+    <para>and to check out the source using a committer user id, use the
     following:</para>
 
-    <programlisting>cvs -d:ext:username at cvs.forge.jboss.com:/cvsroot/jboss checkout JBossRemoting</programlisting>
+    <programlisting>svn checkout https://svn.jboss.org/repos/jbossremoting/remoting2/tags/2.4.0-GA</programlisting>
+    
+    <para>On the other hand, to get the working branch for version 2.4, use</para>
+    
+    <programlisting> svn checkout http://anonsvn.jboss.org/repos/jbossremoting/remoting2/branches/2.x.</programlisting>
 
-    <para>This should checkout the entire remoting project, including doc,
-    tests, libs, etc.</para>
+    <para>or</para>
 
-    <para>See <!--<link linkend="???">http://www.jboss.org/wiki/Wiki.jsp?page=CVSRepository</link>-->
-    <ulink url="http://www.jboss.org/wiki/Wiki.jsp?page=CVSRepository">
-    http://www.jboss.org/wiki/Wiki.jsp?page=CVSRepository </ulink> for more
-    information on how to access the JBoss CVS repository.</para>
+    <programlisting>svn checkout https://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.x.</programlisting>
+    
+    <para>These commands should checkout the entire remoting project, including
+    doc, tests, libs, etc.</para>
+    
+    <para>See <ulink url="http://wiki.jboss.org/wiki/SVNRepository">
+    http://wiki.jboss.org/wiki/SVNRepository</ulink> for more information on how
+    to access the JBoss SVN repository and how to get committer access.</para>
 
     <para>The build process for JBossRemoting is based on a standard ant build
-    file (build.xml). The version of ant that is supported is ant 1.6.2, but
-    should work with earlier versions as there are no special ant features
+    file (build.xml). The version of ant currently in use is ant 1.7.0, but
+    earlier versions should work as well as there are no special ant features
     being used.</para>
 
     <para>The main ant build targets are as follows:</para>
@@ -50,10 +62,15 @@
     <para><emphasis role="bold">tests.quick</emphasis> - runs the functional
     unit tests for JBossRemoting.</para>
 
-    <para><emphasis role="bold">tests</emphasis> - runs all the tests for
-    JBossRemoting, including functional and performance tests for all the
-    different transports.</para>
+    <para><emphasis role="bold">tests</emphasis> - runs all the functional tests
+    for all the different transports.</para>
 
+    <para><emphasis role="bold">tests.performance</emphasis> - runs all the
+    performance tests for all the different transports.</para>
+    
+    <para><emphasis role="bold">tests.versioning.all</emphasis> - runs all the
+    versioning tests for all the different transports.</para>
+
     <para><emphasis role="bold">clean</emphasis> - removes all the build
     artifacts and directories.</para>