Author: buildbot
Date: Fri Jan 18 16:38:07 2013
New Revision: 847178
Log:
Staging update by buildbot for mina
Modified:
websites/staging/mina/trunk/content/ (props changed)
websites/staging/mina/trunk/content/mina-project/sources.html
Propchange: websites/staging/mina/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 18 16:38:07 2013
@@ -1 +1 @@
-1425910
+1435236
Modified: websites/staging/mina/trunk/content/mina-project/sources.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/sources.html (original)
+++ websites/staging/mina/trunk/content/mina-project/sources.html Fri Jan 18
16:38:07 2013
@@ -133,19 +133,17 @@
-<p>Sources for the Apache MINA projects are currently managed through
Subversion (SVN). Instructions on Subversion use can be found at <a
href="http://svnbook.red-bean.com/";>http://svnbook.red-bean.com/</a>. If you
are on Windows, the excellent TortoiseSVN client is highly recommended.</p>
+<p>Sources for the Apache MINA projects are currently managed through GIT.
Instructions on GIT use can be found at <a
href="http://git-scm.com/book/";>http://git-scm.com/book/</a>.</p>
<p>For each project you can find a detailed description how to checkout and
build the source on the project documentation. This page is just a short
overview.</p>
-<h1 id="web-access-to-subversion">Web Access to Subversion</h1>
-<p>If you just want to browse the source code, you can use the <a
href="http://svn.apache.org/viewvc/mina";>web interface to Subversion</a>. This
is current at all times.</p>
-<h1 id="normal-subversion-access">Normal Subversion Access</h1>
-<p>Anyone can check code out of Subversion. You only need to specify a
username and password in order to update the Subversion repository, and only
MINA committers have the permissions to do that. We run Subversion over
standard HTTPS, so hopefully you won't have problems with intervening
firewalls.</p>
-<h1 id="check-out-from-subversion">Check out from Subversion</h1>
+<h1 id="normal-git-access">Normal Git Access</h1>
+<p>Anyone can check code out of Git. You only need to specify a username and
password in order to update the Git repository, and only MINA committers have
the permissions to do that. We run Git over standard HTTPS, so hopefully you
won't have problems with intervening firewalls.</p>
+<h1 id="cloning-from-the-git-repo">Cloning from the Git repo</h1>
<p>Again, anyone can do this. Use a command like to checkout the current
development version (the trunk):</p>
<h3 id="for-mina">For MINA</h3>
-<div class="codehilite"><pre><span class="n">svn</span> <span
class="n">checkout</span> <span class="n">http:</span><span
class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span
class="n">apache</span><span class="o">.</span><span class="n">org</span><span
class="sr">/repos/</span><span class="n">asf</span><span
class="sr">/mina/mi</span><span class="n">na</span><span
class="o">/</span><span class="n">trunk</span>
-</pre></div>
-
-
+<p>read only access :</p>
+<p>git clone http://git-wip-us.apache.org/repos/asf/mina.git mina</p>
+<p>write access :</p>
+<p>git clone https://git-wip-us.apache.org/repos/asf/mina.git mina</p>
<h3 id="for-ftpserver">For FtpServer</h3>
<div class="codehilite"><pre><span class="n">svn</span> <span
class="n">checkout</span> <span class="n">http:</span><span
class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span
class="n">apache</span><span class="o">.</span><span class="n">org</span><span
class="sr">/repos/</span><span class="n">asf</span><span
class="sr">/mina/</span><span class="n">ftpserver</span><span
class="o">/</span><span class="n">trunk</span>
</pre></div>
