Author: ggregory
Date: Sun Jul 21 23:30:36 2019
New Revision: 1863533
URL: http://svn.apache.org/viewvc?rev=1863533&view=rev
Log:
Update SCM info with Git.
Added:
commons/cms-site/trunk/content/xdoc/scminfo.xml
Removed:
commons/cms-site/trunk/content/xdoc/svninfo.xml
Modified:
commons/cms-site/trunk/content/site.xml
commons/cms-site/trunk/content/xdoc/building.xml
commons/cms-site/trunk/content/xdoc/mail-lists.xml
Modified: commons/cms-site/trunk/content/site.xml
URL:
http://svn.apache.org/viewvc/commons/cms-site/trunk/content/site.xml?rev=1863533&r1=1863532&r2=1863533&view=diff
==============================================================================
--- commons/cms-site/trunk/content/site.xml (original)
+++ commons/cms-site/trunk/content/site.xml Sun Jul 21 23:30:36 2019
@@ -140,7 +140,7 @@
</menu>
<menu name="Source Repositories">
- <item name="General Information" href="/svninfo.html"/>
+ <item name="General Information" href="/scminfo.html"/>
<item name="Sandbox"
href="http://svn.apache.org/viewvc/commons/sandbox/"/>
<item name="Dormant"
href="http://svn.apache.org/viewvc/commons/dormant/"/>
</menu>
Modified: commons/cms-site/trunk/content/xdoc/building.xml
URL:
http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/building.xml?rev=1863533&r1=1863532&r2=1863533&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/building.xml (original)
+++ commons/cms-site/trunk/content/xdoc/building.xml Sun Jul 21 23:30:36 2019
@@ -70,7 +70,7 @@
<subsection name='Checking out the Commons sources'>
<p>
Follow the
- <a href="http://commons.apache.org/svninfo.html";>
+ <a href="http://commons.apache.org/scminfo.html";>
Commons subversion instructions</a> to check out the Commons source
files. If you want to build Commons component web sites, you need to have
the <code>commons-build</code> module checked out as a peer to whatever
Modified: commons/cms-site/trunk/content/xdoc/mail-lists.xml
URL:
http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/mail-lists.xml?rev=1863533&r1=1863532&r2=1863533&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/mail-lists.xml (original)
+++ commons/cms-site/trunk/content/xdoc/mail-lists.xml Sun Jul 21 23:30:36 2019
@@ -199,7 +199,7 @@
<td>
<b>Commons Commits List</b>
<br /><br />
- Only for e-mails automatically generated by the <a
href="svninfo.html">source control</a> sytem.
+ Only for e-mails automatically generated by the <a
href="scminfo.html">source control</a> sytem.
<br /><br />
</td>
<td>
Added: commons/cms-site/trunk/content/xdoc/scminfo.xml
URL:
http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/scminfo.xml?rev=1863533&view=auto
==============================================================================
--- commons/cms-site/trunk/content/xdoc/scminfo.xml (added)
+++ commons/cms-site/trunk/content/xdoc/scminfo.xml Sun Jul 21 23:30:36 2019
@@ -0,0 +1,164 @@
+<?xml version="1.0"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<document>
+
+ <properties>
+ <author email="d...@commons.apache.org">The Apache Commons Documentation
Team</author>
+ <title>Source Repositories</title>
+ </properties>
+
+<body>
+
+<section name="About">
+<p>
+This section talks about two version control systems: Git and Subversion.
+For the most part, all <em>current</em> Apache Commons Components use Git.
+Some older inactive components are still in Subversion.
+</p>
+</section>
+
+<section name="Download the Source">
+
+<p>
+Most users of the source code probably don't need to have day to
+day access to the source code as it changes. For these users we
+provide easy-to-unpack source code downloads. See the "Releases"
+link on the Commons page.
+</p>
+
+</section>
+
+<section name="Access the Version Control System (quick info)">
+<p>
+Enter the following URL into a web browser to browse the latest source code,
+or pass that same URL to a git client application to check the code out
+to your local machine, after replacing {component-name} with the appropriate
+value, like lang, io, or text.
+<pre>
+ https://gitbox.apache.org/repos/asf/commons-{component-name}.git
+</pre>
+</p>
+<p>
+Alternatively, enter the following URL into a web browser to browse the latest
+source code including history and commit information.
+<pre>
+ https://gitbox.apache.org/repos/asf/commons-{component-name}
+</pre>
+</p>
+</section>
+
+<section name="Access the Version Control System (details)">
+<p>
+You can get the URL for each component's git repository from that component's
site.
+</p>
+<p>
+Some parts of Commons are still in Subversion, namely, the "sandbox".
+The URLs for direct access to the sandbox section of the Subversion repository
are:
+<ul>
+<li>
+ <a href="http://svn.apache.org/repos/asf/commons";>
+ http://svn.apache.org/repos/asf/commons
+ </a>
+ for non-committers, and
+</li>
+<li>
+ <a href="https://svn.apache.org/repos/asf/commons";>
+ https://svn.apache.org/repos/asf/commons
+ </a>
+ for committers.
+</li>
+</ul>
+</p>
+<p>
+The "proper" subdirectory leads to the old code for official commons
components, before conversion to git.
+The "sandbox" subdirectory leads to the code for experimental commons
components.
+</p>
+<p>
+Subdirectories "trunks-proper" and "trunks-sandbox" are special directories
that
+should be ignored by most users; they have Subversion "external attributes"
+associated with them so that when checking out those directories using a
subversion
+client application, the directory created actually contains the "trunk"
directory
+of every commons or sandbox project. This is useful for special purposes such
as
+building the commons website. Most users can ignore these directories and
access
+the trunk of a project via the "proper" or "sandbox" directory.
+</p>
+<p>
+You can directly browse the <i>pre-git conversion</i> version of ASF the code
in Subversion by entering
+one of the above URLs into a standard web browser. Once you have found a
directory of
+interest, you can pass the same URL to a subversion client in order to check
+out the files locally.
+</p>
+
+<p>
+As an alternative, you can browse the repository (including access to file
history)
+via one of the links below. Once you have found a file or directory of
+interest, replace the url prefix "http://svn.apache.org/viewvc"; with the
+appropriate subversion root url (see above).
+<ul>
+<li><a href="http://svn.apache.org/viewvc/commons/sandbox";>browse sandbox
components via viewer</a></li>
+<li><a href="http://svn.apache.org/viewvc/commons/dormant";>browse dormant
components via viewer</a></li>
+</ul>
+</p>
+
+<p><b>Important!</b> When checking out a directory in subversion, ensure that
you
+do not check out a directory that has "tags" and "branches" subdirectories, as
this will
+result in getting a complete copy of the code for every branch and tag ever
made.
+If you want the latest code, you generally want the directory
<b>{component-name}/trunk</b>,
+though you should check the project directory structure first via one of the
methods
+listed above, as different projects may use different internal directory
structures.
+For example, some projects which support multiple versions of Java may use
+<b>{component-name}/branches/{branch-name}</b> as well as
{component-name}/trunk.
+</p>
+<p>
+<b>Important!</b> At the current time, selecting by date in subversion within
the
+ASF repository isn't reliable. The reason is that when converting a date to a
revision
+number, subversion assumes that revision N has an earlier date than revision
N+M, and
+that it can therefore perform a binary search on revision numbers to locate
one with
+the required date. However CVS imports of data that retain the original date
+information from CVS break this assumption. And unfortunately because revisions
+are repository-wide information, this affects date-based searches
+even in directories unrelated to the ones that CVS stuff was imported into.
+So while dates are reported correctly in "svn log" output, only revision
numbers should
+be used with the -r option. See issue #752 in the subversion issue tracker at
tigris.org.
+</p>
+<p>
+For more information on connecting to the ASF Subversion repository, see the
+<a href="http://www.apache.org/dev/version-control.html";>ASF version control
page</a>.
+</p>
+
+</section>
+
+<section name="About Git">
+<p>
+Git is a free and open source distributed version control system designed to
handle
+everything from small to very large projects with speed and efficiency.
+More information about Git can be found at
+<a href="https://git-scm.com/";>the Git site</a>.
+</p>
+</section>
+
+<section name="About Subversion">
+<p>
+Subversion is an open-source version control system designed to be "a better
CVS".
+More information about subversion can be found at
+<a href="https://subversion.apache.org/";>the Apache Subversion site</a>.
+</p>
+</section>
+
+</body>
+</document>
