pashko/apache-poi
1
0
Fork 0
mirror of https://github.com/apache/poi.git synced 2026-02-27 20:40:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

stray svn refs

Browse Source
This commit is contained in:
PJ Fanning 2025-07-08 03:56:41 +01:00
parent f76089be67
commit ef16723148
8 changed files with 12 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/documentation/content/xdocs/apidocs/index.xml
View File

@ -32,7 +32,7 @@
<p>
The Javadocs for the latest (development) version of Apache POI
can be <a href="dev/index.html">accessed online here</a>, or build
from a <a href="site:subversion">source code checkout</a>
from a <a href="site:git">source code checkout</a>
by running the <em>javadocs</em> Ant task. The
<a href="dev/index.html">latest (development) Javadocs</a> are generally
updated every few weeks, so may lag the most recent development slightly.

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

@ -76,7 +76,7 @@
<strong>not</strong> 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 <a
href="site:subversion">Subversion repository</a>.</note>
href="site:git">Git repository</a>.</note>

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

@ -49,11 +49,10 @@
<em>libgcj </em>, presumably from the same version of GCC with which you compiled.
</p>
</section>
<section><title>Subversion</title>
<section><title>Source Repository</title>
<p>
The POI-Ruby module sits under the POI <a href="https://github.com/apache/poi/tree/trunk/src/contrib/poi-ruby/">Subversion</a>
<a href="https://github.com/apache/poi/tree/trunk/src/contrib/poi-ruby/">(viewvc)</a>. Running <em>make</em>
inside that directory will create a loadable ruby extension <em>poi4r.so</em> in the release subdirectory. Tests
The POI-Ruby module sits under the POI <a href="https://github.com/apache/poi/tree/trunk/src/contrib/poi-ruby/">Git</a>.
Running <em>make</em> inside that directory will create a loadable ruby extension <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>
<p>Note that the makefile, though designed to work across Linux/OS X/Cygwin, has been tested only on linux.

4
src/documentation/content/xdocs/components/spreadsheet/how-to.xml
View File

@ -469,13 +469,13 @@ some of the rows or cells. It can be found at
<code>/poi-examples/src/main/java/org/apache/poi/examples/hssf/eventusermodel/XLS2CSVmra.java</code>,
and may be called on the command line, or from within your own code.
The latest version is always available from
<a href="https://github.com/apache/poi/tree/trunk/poi-examples/src/main/java/org/apache/poi/examples/hssf/eventusermodel/">subversion</a>.
<a href="https://github.com/apache/poi/tree/trunk/poi-examples/src/main/java/org/apache/poi/examples/hssf/eventusermodel/">git</a>.
</p>
<p>
<em>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</em>
<a href="site:subversion">subversion checkout</a>.
<a href="site:git">git checkout</a>.
</p>
</section>

8
src/documentation/content/xdocs/devel/git.xml
View File

@ -46,13 +46,7 @@
</p>
</section>
<section><title>Access the Version Controlled Source Code</title>
<p>
For general information on connecting to the ASF Subversion,
repositories, see the
<a href="https://www.apache.org/dev/version-control.html">version control page.</a>
</p>
<p>Apache POI uses Git as its version control system. We switch from Subversion to Git
<p>Apache POI uses Git as its version control system. We switched from Subversion to Git
in July 2025.
</p>

4
src/documentation/content/xdocs/devel/guidelines.xml
View File

@ -84,7 +84,7 @@
the project vision, etc.</li>
<li>Use POI a bit, look for gaps in the documentation and examples.</li>
<li>Join the <a href="site:mailinglists">mailing lists</a> and share your knowledge with others.</li>
<li>Get <a href="site:subversion">Subversion</a> and check out the POI source tree</li>
<li>Get <a href="site:git">Git</a> and check out the POI source tree</li>
<li>Documentation is always the best place to start contributing, maybe you found that if the documentation just told you how to do X then it would make more sense, modify the documentation.</li>
<li>Contribute examples - if there's something people are often asking about on the <a href="site:mailinglists">user list</a> which isn't covered in the documentation or current examples, try writing an example of this and uploading it as a patch.</li>
<li>Get used to building POI, you'll be doing it a lot, be one with the build, know its targets, etc.</li>
@ -204,7 +204,7 @@
<section><title>Approach 3 - the git way</title>
<p>
If you are working on a Git clone of Apache POI (see the
<a href="site:subversion">Version Control page</a> for
<a href="site:git">Version Control page</a> for
more on the read-only Git mirrors), it is possible to generate
a patch of your changes (including new binary files) using Git.
</p>

2
src/documentation/content/xdocs/help/faq.xml
View File

@ -94,7 +94,7 @@ System.out.println("POI Scratchpad came from " + path);]]></source>
<a href="site:components">the components overview section</a>
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 <a href="site:subversion">subversion</a>,
source code from <a href="site:git">git</a>,
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

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

@ -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
<a href="site:subversion">Subversion Repository</a>,
<a href="site:git">Git Repository</a>,
<a href="site:howtobuild">build the code</a>, join the
<a href="site:mailinglists">mailing lists</a>, and we'll be happy to
help you get started on the project!