From jboss-remoting-commits at lists.jboss.org Sun Jun 8 19:25:36 2008
Content-Type: multipart/mixed; boundary="===============4135900373902983763=="
MIME-Version: 1.0
From: jboss-remoting-commits at lists.jboss.org
To: jboss-remoting-commits at lists.jboss.org
Subject: [jboss-remoting-commits] JBoss Remoting SVN: r4271 -
remoting2/branches/2.x/docs/guide/en.
Date: Sun, 08 Jun 2008 19:25:36 -0400
Message-ID:
--===============4135900373902983763==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: ron.sigal(a)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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- 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 @@
Getting the JBossRemoting source and building
=
- The JBossRemoting source code resides in the JBoss CVS repository
- under the CVS module JBossRemoting. To check out the source using the
+ The JBossRemoting source code resides in the JBoss SVN repositor=
y. The
+ tagged versions are found in
+ https://svn.jboss.org/repos/jbossremoting/remoting2/tags, and the work=
ing
+ branches are found in
+ https://svn.jboss.org/repos/jbossremoting/remoting2/branches.
+ =
+ To check out the source for version 2.4.0.GA using the
anonymous account, use the following command:
=
- cvs -d:pserver:anonymous(a)anoncvs.forge.jboss.com:/cv=
sroot/jboss checkout JBossRemoting
+ svn checkout http://anonsvn.jboss.org/repos/jbossremo=
ting/remoting2/tags/2.4.0-GA.
=
- To check out the source using a committer user id, use the
+ and to check out the source using a committer user id, use the
following:
=
- cvs -d:ext:username(a)cvs.forge.jboss.com:/cvsroot/jbo=
ss checkout JBossRemoting
+ svn checkout https://svn.jboss.org/repos/jbossremoting=
/remoting2/tags/2.4.0-GA
+ =
+ On the other hand, to get the working branch for version 2.4, us=
e
+ =
+ svn checkout http://anonsvn.jboss.org/repos/jbossremo=
ting/remoting2/branches/2.x.
=
- This should checkout the entire remoting project, including doc,
- tests, libs, etc.
+ or
=
- See
-
- http://www.jboss.org/wiki/Wiki.jsp?page=3DCVSRepository for m=
ore
- information on how to access the JBoss CVS repository.
+ svn checkout https://svn.jboss.org/repos/jbossremoting=
/remoting2/branches/2.x.
+ =
+ These commands should checkout the entire remoting project, incl=
uding
+ doc, tests, libs, etc.
+ =
+ See
+ http://wiki.jboss.org/wiki/SVNRepository for more information =
on how
+ to access the JBoss SVN repository and how to get committer access.
=
The build process for JBossRemoting is based on a standard ant b=
uild
- file (build.xml). The version of ant that is supported is ant 1.6.2, b=
ut
- 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 featu=
res
being used.
=
The main ant build targets are as follows:
@@ -50,10 +62,15 @@
tests.quick - runs the functi=
onal
unit tests for JBossRemoting.
=
- tests - runs all the tests for
- JBossRemoting, including functional and performance tests for all the
- different transports.
+ tests - runs all the function=
al tests
+ for all the different transports.
=
+ tests.performance - runs all =
the
+ performance tests for all the different transports.
+ =
+ tests.versioning.all - runs a=
ll the
+ versioning tests for all the different transports.
+
clean - removes all the build
artifacts and directories.
=
--===============4135900373902983763==--