From 0d010235c3c4f369087c1b6a0c1dd4386ec5797d Mon Sep 17 00:00:00 2001 From: Jeremias Maerki Date: Mon, 13 Nov 2006 11:00:48 +0000 Subject: [PATCH] Removing non-existent link. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@474248 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/content/xdocs/dev/tools.xml | 1 - 1 file changed, 1 deletion(-) diff --git a/src/documentation/content/xdocs/dev/tools.xml b/src/documentation/content/xdocs/dev/tools.xml index 325a47ce8..1d0675a10 100644 --- a/src/documentation/content/xdocs/dev/tools.xml +++ b/src/documentation/content/xdocs/dev/tools.xml @@ -124,7 +124,6 @@ Note that this manual applies to the command-line version of SVN.
Integrated Development Environments (IDEs)

An IDE is not required, but will generally be found to be helpful, especially for serious debugging and refactoring.

-

See the Apache Jakarta IDE Developer's Guide for useful information on Java IDEs.

Borland's JBuilder 7/8 does not support Ant builds unless you have the Enterprise Edition (which is quite expensive). This causes problems with any code that is generated by the Ant build. First, you must run the Ant build before you can use the IDE. Second, when you are editing in the IDE, you must be editing the generated files, which means that you must make any changes to the source files in another editor. This is less serious for development on the trunk, but in the maintenance branch, all source files were "generated".

Sun ONE Studio Four does support Ant, but seems to use a built-in version, and as of this writing chokes on the FOP build file, saying that it is not valid. There is awkward because there is no official DTD for Ant, and it may be merely an Ant version issue.

Additional notes on setting up FOP within an IDE (ex. Eclipse) in the Wiki.

-- 2.39.5