The Javadocs for the latest (development) version of Apache POI can be accessed online here, or build - from a source code checkout + from a source code checkout by running the javadocs Ant task. The latest (development) Javadocs are generally updated every few weeks, so may lag the most recent development slightly. diff --git a/src/documentation/content/xdocs/components/hpsf/how-to.xml b/src/documentation/content/xdocs/components/hpsf/how-to.xml index 8b50f1ff2e..a2c7c61acf 100644 --- a/src/documentation/content/xdocs/components/hpsf/how-to.xml +++ b/src/documentation/content/xdocs/components/hpsf/how-to.xml @@ -76,7 +76,7 @@ not present in POI releases up to and including 2.5. In order to write properties you have to download a 3.0.x POI release, or retrieve the POI development version from the Subversion repository. + href="site:git">Git repository. diff --git a/src/documentation/content/xdocs/components/poi-ruby.xml b/src/documentation/content/xdocs/components/poi-ruby.xml index 59cefde764..ba7ceb586e 100644 --- a/src/documentation/content/xdocs/components/poi-ruby.xml +++ b/src/documentation/content/xdocs/components/poi-ruby.xml @@ -49,11 +49,10 @@ libgcj , presumably from the same version of GCC with which you compiled.
-- The POI-Ruby module sits under the POI Subversion - (viewvc). Running make - inside that directory will create a loadable ruby extension poi4r.so in the release subdirectory. Tests + The POI-Ruby module sits under the POI Git. + Running make inside that directory will create a loadable ruby extension 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.
Note that the makefile, though designed to work across Linux/OS X/Cygwin, has been tested only on linux.
diff --git a/src/documentation/content/xdocs/components/spreadsheet/how-to.xml b/src/documentation/content/xdocs/components/spreadsheet/how-to.xml
index 4f51250294..17582e914c 100644
--- a/src/documentation/content/xdocs/components/spreadsheet/how-to.xml
+++ b/src/documentation/content/xdocs/components/spreadsheet/how-to.xml
@@ -469,13 +469,13 @@ some of the rows or cells. It can be found at
/poi-examples/src/main/java/org/apache/poi/examples/hssf/eventusermodel/XLS2CSVmra.java,
and may be called on the command line, or from within your own code.
The latest version is always available from
-subversion.
+git.
In POI versions before 3.0.3, this code lived in the scratchpad section. If you're using one of these older versions of POI, you will either need to include the scratchpad jar on your classpath, or build from a - subversion checkout. + git checkout.
- For general information on connecting to the ASF Subversion, - repositories, see the - version control page. -
- -Apache POI uses Git as its version control system. We switch from Subversion to Git +
Apache POI uses Git as its version control system. We switched from Subversion to Git in July 2025.
diff --git a/src/documentation/content/xdocs/devel/guidelines.xml b/src/documentation/content/xdocs/devel/guidelines.xml index 5442fa1f5e..6f6007227e 100644 --- a/src/documentation/content/xdocs/devel/guidelines.xml +++ b/src/documentation/content/xdocs/devel/guidelines.xml @@ -84,7 +84,7 @@ the project vision, etc.If you are working on a Git clone of Apache POI (see the - Version Control page for + Version Control page for more on the read-only Git mirrors), it is possible to generate a patch of your changes (including new binary files) using Git.
diff --git a/src/documentation/content/xdocs/help/faq.xml b/src/documentation/content/xdocs/help/faq.xml index 2c083335b0..28541a1146 100644 --- a/src/documentation/content/xdocs/help/faq.xml +++ b/src/documentation/content/xdocs/help/faq.xml @@ -94,7 +94,7 @@ System.out.println("POI Scratchpad came from " + path);]]> the components overview section for the artifact details to have maven download it for you. If you download the source release of POI, and/or checkout the - source code from subversion, + source code from git, then you can run the ant task "compile-ooxml-xsds" to have the OOXML schemas downloaded and compiled for you (This will also give you the XMLBeans generated source code, in case you wish to diff --git a/src/documentation/content/xdocs/index.xml b/src/documentation/content/xdocs/index.xml index b96aece515..f0c816d6be 100644 --- a/src/documentation/content/xdocs/index.xml +++ b/src/documentation/content/xdocs/index.xml @@ -236,7 +236,7 @@ hard-working, talented folks to help us on the project, no matter your background. So if you're motivated, ready, and have the time: Download the source from the - Subversion Repository, + Git Repository, build the code, join the mailing lists, and we'll be happy to help you get started on the project!