moparisthebest
/
poi
1
0
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity

Replaced "CVS" in the top-lvel files by "Subversion". 

git-svn-id: https://svn.apache.org/repos/asf/jakarta/poi/trunk@376062 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Rainer Klute 2006-02-08 20:50:58 +00:00
parent 3258401397
commit 3dae9ee8ef
6 changed files with 36 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/documentation/content/xdocs/book.xml
View File

@ -58,13 +58,10 @@
</menu>
<menu label="Code">
<!-- <menu-item label="Source Code" href="http://jakarta.apache.org/poi/javadocs/javasrc/"/> -->
<menu-item label="CVS" href="http://jakarta.apache.org/site/cvsindex.html"/>
<!-- <menu-item label="CVS Changelog" href="changelog.html"/> -->
<menu-item label="Subversion (current source code)" href="http://jakarta.apache.org/site/cvsindex.html"/>
<menu-item label="Top Voted Bugs" href="http://issues.apache.org/bugzilla/buglist.cgi?votes=1&amp;product=POI&amp;order=bugs.votes"/>
<menu-item label="Bug Database" href="http://issues.apache.org/bugzilla/buglist.cgi?product=POI"/>
<menu-item label="Patches" href="http://issues.apache.org/bugzilla/buglist.cgi?product=POI&amp;short_desc=%5BPATCH%5D&amp;short_desc_type=allwordssubstr"/>
<menu-item label="Junit Test Results" href="ext:junit"/>
<menu-item label="Dependency Metrics" href="ext:jdepend"/>
<!-- <menu-item label="Checkstyle Metrics" href="http://jakarta.apache.org/poi/metrics/checkstyle/"/> -->

2
src/documentation/content/xdocs/casestudies.xml
View File

@ -138,7 +138,7 @@ format,
Managament and Maintenance System for the Telecommunications industry
based
on Turbine and Velocity. Originally the invoicing was done with a simple
CVS
CSV
sheet which was then marked up by accounts and customized for each client.
As growth has been consistent with the application, the requirement for
invoices that need not be touched by hand increased. POI provided the

2
src/documentation/content/xdocs/hpsf/how-to.xml
View File

@ -48,7 +48,7 @@
details! <strong>Please note:</strong> HPSF's writing functionality is
<strong>not</strong> present in POI releases up to and including 2.5. In
order to write properties you have to download a later POI release (when
available) or retrieve the POI development version from the CVS
available) or retrieve the POI development version from the Subversion
repository.
</li>
</ol>

22
src/documentation/content/xdocs/index.xml
View File

@ -92,8 +92,8 @@
<p>HPSF supports reading and writing of properties. However, with the
current POI release only reading is possible. In order to write
properties, you'll have to fetch the latest POI version <link
href="http://jakarta.apache.org/site/cvsindex.html">from the CVS
repository</link>.</p>
href="http://jakarta.apache.org/site/cvsindex.html">from the
Subversion repository</link>.</p>
<p>Please see <link href="./hpsf/index.html">the HPSF project
page</link> for more information.</p>
@ -124,3 +124,21 @@
</legal>
</footer>
</document>
<!-- Keep this comment at the end of the file
Local variables:
mode: xml
sgml-omittag:nil
sgml-shorttag:nil
sgml-namecase-general:nil
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->

21
src/documentation/content/xdocs/patches.xml
View File

@ -35,16 +35,17 @@
<link href="contrib.xml">Third-Party
Contributions</link>. The preferred submission method for patches is:
</p>
<ul>
<li>Post to POI developers list</li>
<li>Describe the patch, the reason for it and (if necessary) why this is important.</li>
<li>Generate the patch in
<code>diff -u</code> format from CVS
</li>
<li>Also generate a documentation patch or new file, if this is something that should be documented.
</li>
<li>Post as an attachment rather than inline (unless it is trivially small).</li>
</ul>
<ul>
<li>Post to POI developers list</li>
<li>Describe the patch, the reason for it and (if necessary) why this
is important.</li>
<li>Generate the patch in the unified diff format. This format is
created by the typical Subversion client when you execute the
<code>svn diff</code> command or the equivalent of it in a GUI environment.</li>
<li>Also generate a documentation patch or new file, if this is
something that should be documented.</li>
<li>Post as an attachment rather than inline (unless it is trivially small).</li>
</ul>
<p>Following the above guidelines will facilitate your patch being reviewed
and applied efficiently.</p>
</section>

4
src/documentation/content/xdocs/poi-ruby.xml
View File

@ -32,9 +32,9 @@
<em>libgcj </em>, presumably from the same version of GCC with which you compiled.
</p>
</section>
<section><title>CVS</title>
<section><title>Subversion</title>
<p>
The POI-Ruby module sits under the POI <link href="http://jakarta.apache.org/site/cvsindex.html">CVS</link> in the <em>src/contrib/poi-ruby</em> directory. Running <em>make</em>
The POI-Ruby module sits under the POI <link href="http://jakarta.apache.org/site/cvsindex.html">Subversion</link> in the <em>src/contrib/poi-ruby</em> directory. Running <em>make</em>
inside that directory will create a loadable ruby extention <em>poi4r.so</em> in the release subdirectory. Tests
are in the <em>tests/</em> subdirectory, and should be run from the <em>poi-ruby</em> directory. Please read the tests to figure out the usage.
</p>