Author: mrdon
Date: Thu Oct 14 15:38:10 2004
New Revision: 54808
Modified:
struts/trunk/xdocs/acquiring.xml
struts/trunk/xdocs/faqs/helping.xml
struts/trunk/xdocs/faqs/kickstart.xml
struts/trunk/xdocs/navigation.xml
struts/trunk/xdocs/project.xml
struts/trunk/xdocs/releases.xml
struts/trunk/xdocs/userGuide/installation-1.0.xml
struts/trunk/xdocs/userGuide/installation.xml
struts/trunk/xdocs/using.xml
Log:
Changed CVS references to Subversion references including viewcvs URL's.
Commented out CVS links that didn't have a Subversion equivalent
Modified: struts/trunk/xdocs/acquiring.xml
==============================================================================
--- struts/trunk/xdocs/acquiring.xml (original)
+++ struts/trunk/xdocs/acquiring.xml Thu Oct 14 15:38:10 2004
@@ -71,19 +71,19 @@
<li>
Nightly builds - Download the source directly via
- <a href="http://jakarta.apache.org/getinvolved/cvsindex.html";>
- Anonymous CVS</a>.
+ <a href="http://www.apache.org/dev/version-control.html";>
+ Anonymous Subversion</a>.
</li>
<li>
Nightly builds - Download the binary distributions from the
- <a href="http://cvs.apache.org/builds/jakarta-struts/nightly";>
+ <a href="http://svn.apache.org/builds/struts/nightly/";>
Struts nightly builds directory</a>.
</li>
<li>
Nightly builds - Download the source distributions from the
- <a href="http://cvs.apache.org/builds/jakarta-struts/nightly/src";>
+ <a href="http://svn.apache.org/builds/struts/nightly/src/";>
Struts nightly build source directory</a>.
</li>
@@ -101,7 +101,7 @@
If you are interested in the Tag Library Descriptor (TLD) files,
they are maintained in the
<a href="http://svn.apache.org/repos/asf/struts/trunk/conf/share/";>
- /conf/share</a> folder of he main repository.
+ /conf/share</a> folder of the main repository.
</p>
<p>
@@ -111,11 +111,11 @@
</p>
<p>
- Access to the CVS source repository for Struts is available through both
- <a href="http://cvs.apache.org/viewcvs/jakarta-struts/";>web browser</a>
+ Access to the Subversion repository for Struts is available through both
+ <a href="http://svn.apache.org/viewcvs.cgi/struts/trunk/?root=Apache-SVN";>web
browser</a>
and
- <a href="http://jakarta.apache.org/getinvolved/cvsindex.html";>
- CVS client</a> interfaces.
+ <a href="http://www.apache.org/dev/version-control.html";>
+ Subversion client</a> interfaces.
</p>
</section>
Modified: struts/trunk/xdocs/faqs/helping.xml
==============================================================================
--- struts/trunk/xdocs/faqs/helping.xml (original)
+++ struts/trunk/xdocs/faqs/helping.xml Thu Oct 14 15:38:10 2004
@@ -301,7 +301,7 @@
and whether what is being developed will meet your needs.
If you need a feature right now, you can use the nightly build, or roll your
own patch.
-There are no private CVS's or private development lists.
+There are no private Subversion repositories or private development lists.
What you see is what we got.
If you are following the DEV list, then you know everything the developers
know.
Modified: struts/trunk/xdocs/faqs/kickstart.xml
==============================================================================
--- struts/trunk/xdocs/faqs/kickstart.xml (original)
+++ struts/trunk/xdocs/faqs/kickstart.xml Thu Oct 14 15:38:10 2004
@@ -128,7 +128,7 @@
<p>
For static unit tests, we use the <a href="http://www.junit.org";>JUnit framework</a>.
The sources for these tests are in the "src/test"
-hierarchy in the CVS repository, and are executed via the "test.junit"
+hierarchy in the Subversion repository, and are executed via the "test.junit"
target in the top-level build.xml file. Such tests are focused on the
low-level functionality of individual methods, are particularly
suitable for the static methods in the org.apache.struts.util utility
Modified: struts/trunk/xdocs/navigation.xml
==============================================================================
--- struts/trunk/xdocs/navigation.xml (original)
+++ struts/trunk/xdocs/navigation.xml Thu Oct 14 15:38:10 2004
@@ -56,9 +56,13 @@
</menu>
<menu name="Development">
- <item name="CVS Access" href="cvs-usage.html"/>
- <item name="CVS Repository"
href="http://cvs.apache.org/viewcvs/jakarta-struts/"/>
- <item name="CVS Changelog" href="changelog-report.html"/>
+ <!-- cvs-usage.html doesn't exist so I'm commenting this out
+ <item name="CVS Access" href="cvs-usage.html"/>
+ -->
+ <item name="Subversion Repository"
href="http://svn.apache.org/repos/asf/struts/trunk/"/>
+ <!-- Is there a Subversion equivalent?
+ <item name="Subversion Changelog" href="changelog-report.html"/>
+ -->
<item name="File Activity" href="file-activity-report.html"/>
<item name="Build Dependencies" href="dependencies.html"/>
<item name="Release Guidelines" href="releases.html"/>
Modified: struts/trunk/xdocs/project.xml
==============================================================================
--- struts/trunk/xdocs/project.xml (original)
+++ struts/trunk/xdocs/project.xml Thu Oct 14 15:38:10 2004
@@ -81,12 +81,16 @@
</menu>
<menu name="Development">
+ <!-- Not sure what would go here for Subversion
<item name="CVS Access" href="reports/cvs-usage.html"/>
+ -->
<item
- name="CVS Repository"
- href="http://cvs.apache.org/viewcvs/jakarta-struts/";
+ name="Subversion Repository"
+ href="http://svn.apache.org/viewcvs.cgi/struts/trunk/?root=Apache-SVN/";
/>
+ <!-- Again, is there a Subversion equivalent?
<item name="CVS Changelog" href="reports/changelog-report.html"/>
+ -->
<item name="File Activity" href="reports/file-activity-report.html"/>
<item name="Build Dependencies" href="reports/dependencies.html"/>
<item
Modified: struts/trunk/xdocs/releases.xml
==============================================================================
--- struts/trunk/xdocs/releases.xml (original)
+++ struts/trunk/xdocs/releases.xml Thu Oct 14 15:38:10 2004
@@ -33,7 +33,7 @@
<p>
A fully-compatible point release does not always need a "preview" beta or
milestone release.
If appropriate, a Release Candidate can be cut, uploaded to the Release
Manager's home directory
- on cvs.apache.org (~/public_html), and voted to be released to the
general public from there.
+ on svn.apache.org (~/public_html), and voted to be released to the
general public from there.
</p>
<p>
Modified: struts/trunk/xdocs/userGuide/installation-1.0.xml
==============================================================================
--- struts/trunk/xdocs/userGuide/installation-1.0.xml (original)
+++ struts/trunk/xdocs/userGuide/installation-1.0.xml Thu Oct 14 15:38:10 2004
@@ -268,7 +268,7 @@
(required only if you wish to use the <code>deploy.catalina</code>
target).</li>
</ul></li>
- <li>If you are a Struts developer with write access to the CVS repository,
+ <li>If you are a Struts developer with write access to the Subversion repository,
be sure that you do <strong>NOT</strong> check in a copy of the
<code>build.properties</code> file, since it will be different for
each individual developer.</li>
Modified: struts/trunk/xdocs/userGuide/installation.xml
==============================================================================
--- struts/trunk/xdocs/userGuide/installation.xml (original)
+++ struts/trunk/xdocs/userGuide/installation.xml Thu Oct 14 15:38:10 2004
@@ -363,7 +363,7 @@
</ul></li>
- <li>If you are a Struts developer with write access to the CVS repository,
+ <li>If you are a Struts developer with write access to the Subversion repository,
be sure that you do <strong>NOT</strong> check in a copy of the
<code>build.properties</code> file, since it will be different for
each individual developer.</li>
Modified: struts/trunk/xdocs/using.xml
==============================================================================
--- struts/trunk/xdocs/using.xml (original)
+++ struts/trunk/xdocs/using.xml Thu Oct 14 15:38:10 2004
@@ -78,7 +78,8 @@
</p>
<p>
- The documentation is maintained in the <code>doc</code> folder of the CVS
+ The documentation is maintained in the <code>doc</code> folder of the Subversion
+ repository
in a XML format.
In the Nightly Build, there is a "compile.website" target in the
<code>build.xml</code> file, which renders the XML into the HTML we post
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
