diff --git a/src/documentation/content/xdocs/book.xml b/src/documentation/content/xdocs/book.xml index 13538d3e9..7da92a665 100644 --- a/src/documentation/content/xdocs/book.xml +++ b/src/documentation/content/xdocs/book.xml @@ -58,13 +58,10 @@ - - - + - diff --git a/src/documentation/content/xdocs/casestudies.xml b/src/documentation/content/xdocs/casestudies.xml index 6f578cf0c..ae1b52545 100644 --- a/src/documentation/content/xdocs/casestudies.xml +++ b/src/documentation/content/xdocs/casestudies.xml @@ -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 diff --git a/src/documentation/content/xdocs/hpsf/how-to.xml b/src/documentation/content/xdocs/hpsf/how-to.xml index 1098a6710..b99368514 100644 --- a/src/documentation/content/xdocs/hpsf/how-to.xml +++ b/src/documentation/content/xdocs/hpsf/how-to.xml @@ -48,7 +48,7 @@ details! Please note: HPSF's writing functionality is not 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. diff --git a/src/documentation/content/xdocs/index.xml b/src/documentation/content/xdocs/index.xml index cd0b32928..642689970 100644 --- a/src/documentation/content/xdocs/index.xml +++ b/src/documentation/content/xdocs/index.xml @@ -92,8 +92,8 @@

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 from the CVS - repository.

+ href="http://jakarta.apache.org/site/cvsindex.html">from the + Subversion repository.

Please see the HPSF project page for more information.

@@ -124,3 +124,21 @@ + + diff --git a/src/documentation/content/xdocs/patches.xml b/src/documentation/content/xdocs/patches.xml index d81c3380e..0079aa3c8 100644 --- a/src/documentation/content/xdocs/patches.xml +++ b/src/documentation/content/xdocs/patches.xml @@ -35,16 +35,17 @@ Third-Party Contributions. The preferred submission method for patches is:

-
    -
  • Post to POI developers list
    • -
  • Describe the patch, the reason for it and (if necessary) why this is important.
    • -
  • Generate the patch in - diff -u format from CVS -
    • -
  • Also generate a documentation patch or new file, if this is something that should be documented. -
    • -
  • Post as an attachment rather than inline (unless it is trivially small).
    • -
+
    +
  • Post to POI developers list
    • +
  • Describe the patch, the reason for it and (if necessary) why this + is important.
    • +
  • Generate the patch in the unified diff format. This format is + created by the typical Subversion client when you execute the + svn diff command or the equivalent of it in a GUI environment.
    • +
  • Also generate a documentation patch or new file, if this is + something that should be documented.
    • +
  • Post as an attachment rather than inline (unless it is trivially small).
    • +

Following the above guidelines will facilitate your patch being reviewed and applied efficiently.

diff --git a/src/documentation/content/xdocs/poi-ruby.xml b/src/documentation/content/xdocs/poi-ruby.xml index 4b7d00e9e..11a96b591 100644 --- a/src/documentation/content/xdocs/poi-ruby.xml +++ b/src/documentation/content/xdocs/poi-ruby.xml @@ -32,9 +32,9 @@ libgcj , presumably from the same version of GCC with which you compiled.

-
CVS +
Subversion

- The POI-Ruby module sits under the POI CVS in the src/contrib/poi-ruby directory. Running make + The POI-Ruby module sits under the POI Subversion in the src/contrib/poi-ruby directory. Running make inside that directory will create a loadable ruby extention poi4r.so in the release subdirectory. Tests are in the tests/ subdirectory, and should be run from the poi-ruby directory. Please read the tests to figure out the usage.