larryi 01/09/19 21:28:09
Modified: . README
Log:
Miscellaneous updates. Document warnings that occur when using Ant 1.4.
Also document that Jikes 1.14-1 or later is needed to pass all the internal
tests if Jikes is used as the Java compiler for JSP.
Revision Changes Path
1.18 +24 -12 jakarta-tomcat/README
Index: README
===================================================================
RCS file: /home/cvs/jakarta-tomcat/README,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- README 2001/07/20 12:50:29 1.17
+++ README 2001/09/20 04:28:09 1.18
@@ -22,16 +22,23 @@
("%JAVA_HOME%\bin" for Windows) to your PATH. Configure the CLASSPATH
environment variable as well, if required.
-* Download the Ant version 1.3 binary distribution from
- <http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin> and install
+* Download the Ant version 1.3 (or 1.4) binary distribution from
+ <http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin> (or
+ <http://jakarta.apache.org/builds/jakarta-ant/release/v1.4/bin>) and install
it in the $JAKARTA_HOME directory. Set an "ANT_HOME" environment variable
- to point to $JAKARTA_HOME/jakarta-ant-1.3. If you are using Windows 9x,
- you should set ANT_HOME using the DOS 8.3 name. Also, add "$ANT_HOME/bin"
- (%ANT_HOME%/bin for Windows) to your PATH.
+ to point to $JAKARTA_HOME/jakarta-ant-1.3 (or $JAKARTA_HOME/jakarta-ant-1.4).
+ If you are using Windows 9x, you should set ANT_HOME using the DOS 8.3 name,
+ In this case, you may find it convenient to rename the directory to a name
+ that is within the DOS 8.3 format, such as "ant-1.3" (or "ant-1.4").
+ Also, add "$ANT_HOME/bin" (%ANT_HOME%/bin for Windows) to your PATH.
+
+ Note: If you build with Ant 1.4, you will receive "deprecation" warnings for
+ the use of the "cr" attribute on the "fixcrlf" task. This is normal and
+ not an indication of an error.
* If you want to include SSL support, download the Java Secure Sockets
Extension (JSSE) implementation (current version number is 1.0.2) from
- <http://java.sun.com/products/jsse> and install it into $JAKARTA_HOME.
+ <http://java.sun.com/products/jsse/> and install it into $JAKARTA_HOME.
* Obtain the following source distribution(s) either from anonymous CVS (see
<http://jakarta.apache.org/site/cvsindex.html> for details) or by
@@ -48,7 +55,6 @@
jakarta-tomcat
jsse1.0.2 optional
-
* You can now build an "unpacked" version of Tomcat (builds quicker because
no time is spent JARing up results) by executing the following commands:
@@ -143,12 +149,12 @@
XML Parsing specification. Parsers known to successfully run Tomcat include:
* The JAXP reference implementation (version 1.0 or later), which can be
- downloaded from <http://java.sun.com/xml>. JAXP version 1.1 is
- included in the Tomcat binary distribution.
+ downloaded from <http://java.sun.com/xml/download.html>. JAXP version 1.1
+ is included in the Tomcat binary distribution.
* The Xerces parser (version 1.1.2 or later), which can be downloaded
from <http://xml.apache.org>. Make sure that the "xerces.jar" replaces
- jaxp.jar and parser.jar in Tomcat's lib/container directory.
+ jaxp.jar and crimson.jar in Tomcat's lib/container directory.
Testing the Build
@@ -171,10 +177,10 @@
"trusted". This can be accomplished by executing the following:
cd $JAKARTA_HOME/jakarta-tomcat/build/tomcat <-- Unix
- ./bin/tomcat.sh run -enableAdmin
+ ./bin/tomcat.sh enableAdmin
cd %JAKARTA_HOME%\jakarta-tomcat\build\tomcat <-- Windows
- bin\tomcat run -enableAdmin
+ bin\tomcat enableAdmin
Next, start Tomcat with:
@@ -191,6 +197,12 @@
followed the "PASSED Tests". This same procedure will also work with the
binary distribution which is created in
"$JAKARTA_HOME/jakarta-tomcat/dist/tomcat".
+
+If you use Jikes as the JSP page Java compiler, you will need version
+1.14-1 or later to run the tests without error. Some tests will fail
+due to Java compilation errors if an earlier Jikes compiler is used.
+See <http://oss.software.ibm.com/developerworks/opensource/jikes/> for
+the latest version.
For security reasons, after you are done with the test, you should either
restore the Admin web application to the default "untrusted" state, or change
