From 9a6bb29965e0e6daa71f3c27641af9104f5af433 Mon Sep 17 00:00:00 2001 From: Glen Mazza Date: Mon, 3 Jan 2005 22:39:27 +0000 Subject: Removed URL references to nagoya. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@198220 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/content/xdocs/dev/api-doc.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/documentation/content/xdocs/dev') diff --git a/src/documentation/content/xdocs/dev/api-doc.xml b/src/documentation/content/xdocs/dev/api-doc.xml index eded42ad9..d63a27f59 100644 --- a/src/documentation/content/xdocs/dev/api-doc.xml +++ b/src/documentation/content/xdocs/dev/api-doc.xml @@ -25,12 +25,12 @@
On-line Access (through Gump) -

FOP (and many other Apache projects) use Apache Gump to do a test build several times each day. One of the useful byproducts of this process is that javadocs can be created and made available.

+

FOP (and many other Apache projects) use Apache Gump to do a test build several times each day. One of the useful byproducts of this process is that javadocs can be created and made available.

First, determine which line of development code you wish to see. If you don't know, you probably want the "Maintenance Branch", which is the line that currently produces FOP releases. See Development Lines for more details.

Javadocs for both development lines are made from current CVS code, and are not tied to any particular release. Both the documentation and the API may be different, even if you are working with the correct branch. Currently, the only way to obtain API documentation for a specific release is to build it yourself. If the links return an "Object not found!" message or otherwise do not work properly, it is probably because of a build error. Please raise a question on the fop-user mailing list so that any problems can be fixed before the next build.
-- cgit v1.2.3